Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

NiFi Crash after runing chain of lookups

avatar
Rising Star

Hi all,

My nifi crash for some reasons that I could not figure out, can anyone helps?

1. A chain of lookups that I have, the table being looked up contains around 50,000,000 rows

jarviszzzz_0-1704952753627.png

2. After running some node, it crashed like this:

jarviszzzz_1-1704953193086.png

3. After this, I relogged into NiFi to see what error happened:

jarviszzzz_2-1704953551268.png

My Lookup service setup:

jarviszzzz_3-1704953607188.pngjarviszzzz_4-1704953620484.pngjarviszzzz_5-1704953633546.png

jarviszzzz_6-1704953647052.png

I can provide more details upon request.

Please help!!!Thanks

 

 

1 ACCEPTED SOLUTION

avatar
Master Guru

make sure you are running 1.24 or 2.0 nifi.

 

Add more connections in your pool, maybe 32

make sure you mysql has enough ram and cores, also make sur eyou have a fast network between them

 

restart after you update the conf/bootstrap.conf

 

java.arg.2=-Xms64G
java.arg.3=-Xmx128G

change lookup

View solution in original post

5 REPLIES 5

avatar
Community Manager

@jarviszzzz, Welcome to our community! To help you get the best possible answer, I have tagged in our NiFi @cotopaul @SAMSAL @TimothySpann experts who may be able to assist you further.

Please feel free to provide any additional information or details about your query, and we hope that you will find a satisfactory solution to your question.



Regards,

Vidya Sargur,
Community Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community:

avatar
Master Guru

How many nodes?  How much RAM and CPUs per node?  Which version of NiFi?   Which version of JDK?

 

I recommend 128GB RAM, 32cores, 6 nodes+, JDK 21.

Also for that many rows you probably want to use a real database and not the tiny cache server.   I would say Redis could work.

avatar
Rising Star

Dear Timothy,

I actually figured out the reason why it crash, so I change my local pc to a CPU server.

Below is the Pics for CPU and RAM:

jarviszzzz_0-1705027528018.png

I am actually using two server for this NiFi operation, one is holding Mysql Server, another one is for NiFi.

However, It still shows slowness for running the lookup processor. How can I make it faster? Thank you so much.


Please let me know if any other information that you need

avatar
Master Guru

make sure you are running 1.24 or 2.0 nifi.

 

Add more connections in your pool, maybe 32

make sure you mysql has enough ram and cores, also make sur eyou have a fast network between them

 

restart after you update the conf/bootstrap.conf

 

java.arg.2=-Xms64G
java.arg.3=-Xmx128G

change lookup

avatar
Rising Star

Hi Timothy,

Thank you so much for helping. I also made some changes (adding index, change data types etc.,) for mysql database. Now, it ran much faster than before