NiFi PutHBaseCell failing

Multi tool use
Multi tool useThe name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP


NiFi PutHBaseCell failing



I am writing data to HBase with NiFi (v1.4) using PutHBase cell, we process ~300 million inserts a day. At times we receive bulletins:



Failed to send StandardFlowFileRecord...to HBase due to RetriesExhaustedWithDetailsException: Failed x actions: ConnectionClosingException: y times, IOException: z times, routing to failure



I have routed failure back into PutHBaseCell - my understanding is periodic failure is expected/normal when HBase is splitting a region, and indeed after a short period of time the failed records are successfully inserted.



However, at least once a day, this issue does not clear up. The error above appears in the NiFi logs w/o end, and the only way we are able to fix it is to restart NiFi, only to see it happen again in a day or so.



Any ideas on how to investigate/correct this issue would be immensely appreciated. Our HBase/Hadoop (Cloudera distribution) admin has not found a smoking gun on the HBase side of things (HBase config and logs).









By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Jad4Du027Gpyq3Y1ohn,JMF PXMjrb7cMav5MT4,0wq4uMhfX1F xFr63fxbuhBqKzSfh7Kc3kWx VOrL,XkG1UhGw5PGD 6900t61IeS
-
fGiBy 4S731Lztw

Popular posts from this blog

Visual Studio Code: How to configure includePath for better IntelliSense results

Image
Clash Royale CLAN TAG #URR8PPP Visual Studio Code: How to configure includePath for better IntelliSense results so I am a complete beginner to using Visual Studio Code and I have no clue what I am doing. I've searched around (maybe not enough), but I cant find just a simple explanation for someone like me on how to configure the c_cpp_properties.json file that I am redirected to whenever I click on the yellow lightbulb next to a line that is underlined with a green squiggle. Lightbulb example c_cpp_properties.json I just want to know what to put in the .json to make IntelliSense work properly This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. 2 Answers 2 From: https://code.visualstudio.com/docs/languages/cpp Below you can see that the MinGW C++ include path has been added to browse.path for Windows: { "name": "Win32...
Read more

Spring cloud config client Could not locate PropertySource

Image
Clash Royale CLAN TAG #URR8PPP Spring cloud config client Could not locate PropertySource My config server use natie file system works fine and the dev profile configured contextPath: /config spring: application: name: dcit-config profiles: active: native management: endpoints: web: exposure: include: info, health, metrics metrics: export: atlas: enabled: true --- spring: profiles: native application: name: dcit-config cloud: config: server: native: searchLocations: classpath:/config/ server: port: 2003 eureka: instance: prefer-ip-address: true lease-renewal-interval-in-seconds: 5 lease-expiration-duration-in-seconds: 20 client: serviceUrl: defaultZone: http://dcit:dcit@localhost:1023/eureka registry-fetch-interval-seconds: 10 --- spring: profiles: dev application: name: dcit-config cloud: config: server: git: uri: http://xxx/gi...
Read more

Makefile test if variable is not empty

Makefile test if variable is not empty In a makefile I'm trying to I've created this simplified makefile to demonstrate my problem. Neither make a or make b executes the body of the if, I don't understand why not. make a make b .PHONY: a b a: $(eval MY_VAR = $(shell echo whatever)) @echo MY_VAR is $(MY_VAR) $(info $(MY_VAR)) ifneq ($(strip $(MY_VAR)),) @echo "should be executed" endif @echo done b: $(eval MY_VAR = $(shell echo '')) @echo MY_VAR is $(MY_VAR) $(info $(MY_VAR)) ifneq ($(strip $(MY_VAR)),) @echo "should not be executed" endif @echo done I'm using $ make --version GNU Make 3.81 There are several problems, and misunderstandings. Your MY_VAR is a make variable, set it without a <tab> to its value, and no need to $(eval ...) . MY_VAR:=$(shell echo whatever) is enough. No <tab> before $(info ...) neither, this is make – Zelnes ...
Read more