Member since
07-07-2022
7
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1610 | 08-05-2022 03:26 PM |
09-04-2022
04:19 PM
@araujo Thank you for the help.. It works.
... View more
09-02-2022
12:22 AM
Hi, In a clustered nifi setup, if a node which has some flow files queued goes down and cant be brought back up, i understand manual intervention is required to redirect the flow files from crashed node to active node. I tried copying the flow files from flowfile and content repository of crashed node to active node. But it didnt help. Can anyone please help with what has to be done to redirect the flow files from crashed node to active node? Thanks
... View more
Labels:
- Labels:
-
Apache NiFi
08-08-2022
05:43 AM
1 Kudo
@nk20 I am confused by your concern about in memory state. Can you provide more detail around what you are being told or what you have read that has lead to this concern? Perhaps those concerns are about something more than component state? Perhaps I can address those specific concerns. Not all NiFi components retain state. Those that do either persist that state to disk in a local state directory or write that state to zookeeper. As long as that local disk where state directory is persisted is not lost and the Zookeeper has quorum (min three nodes), then you have your state protected for your NiFi components that write state. Out of all the components (processors, controller services, reporting tasks, etc), there are only about 25 that record state. The only thing that lives in memory only is component status (in, out, read, write, send, received). These are 5 minute stats that live in memory and thus any restart of the NiFi service would set these stats back to 0. These have nothing to do with the FlowFiles or execution of the processor. If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt
... View more
07-10-2022
04:15 AM
@hegdemahendra Thank you for your reply.. It will be a continuous migration that will run for few months... Once all the historic data is migrated, it will be a CDC. The no of tables could be close to 20-30 tables.. I dont know yet about the volume but it will be huge... Based on your response, the solution looks like the combined approach for multiple tables and CDC. Could you please share little more details about this approach?
... View more