Whenever a nifi node from nifi cluster disconnects and restart again . Sometimes it give error related to corrupted flow file.
This problem requires manual intervention. We have to delete flow.xm.gz and flow.json.gz file /opt/nifi/data folder and then restart that node. Then that node copies these files from primary node.
Solution: can we automate this process. Whenever this issue occurs , non-promary node archive the old flow file and copy new files from primary node.
We have this issue with NiFi nodes outside of Kubernetes as well. I think this type of thing should be considered outside of the scope of a NiFi helm chart. It's more of an application issue.
Problem :
Whenever a nifi node from nifi cluster disconnects and restart again . Sometimes it give error related to corrupted flow file.
This problem requires manual intervention. We have to delete flow.xm.gz and flow.json.gz file /opt/nifi/data folder and then restart that node. Then that node copies these files from primary node.
Solution: can we automate this process. Whenever this issue occurs , non-promary node archive the old flow file and copy new files from primary node.