Member since
11-11-2024
3
Posts
2
Kudos Received
0
Solutions
11-19-2024
09:01 PM
Thank you for your reply. I just tried deploying a NiFi container without modifying the start.sh script, and I found that when I set NIFI_CLUSTER_IS_NODE to true, the container still gets stuck and then stops. I find this strange—if the container doesn’t support clustering, why does the official image allow this environment variable to be set? I think this is misleading. I noticed that version 2.0.0 supports setting nifi.cluster.leader.election.implementation to KubernetesLeaderElectionManager. Does this require NiFi to be deployed at the same level as Kubernetes, or does NiFi need to be deployed as a pod within Kubernetes? I look forward to your response. Thank you!
... View more
11-12-2024
06:17 AM
@ZNFY Since you are exporting a flow definition of a process group, you'll need to utilize the MiNiFi toolkit to transform it in to the proper format that can be loaded by MiNiFi. The MiNiFi-toolkit can be downloaded from here: https://nifi.apache.org/download/ (select "MINIFI' and click download link for Toolkit). Execute: ./minifi-toolkit/bin/config.sh transform-nifi <exported flow definition> flow.json.raw Now edit the flow.json.raw file and edit the following property at start of file (value can not be 0.) "maxTimerDrivenThreadCount":5 Now you can start your MiNiFi and it will create the flow.json.gz as it starts. Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt
... View more