I have a cluster that is running production and the nodes within the cluster keep falling out. The flow.tar is stuck in flow.tar.stale but I can't tell which server is causing the timing issue. In ApacheNIFI, which conf property actually increases the setting for the node to respond? I see:
nifi.cluster.manager.flow.retrieval.delay description: the delay before the cluster manager retrieves the latest flow configuration. But I thought this pulled the flow.xml out of memory to save to disk. What I need is to increase the time before a node drops out of the cluster because the flow.tar is stale. Also, it would be great if in the logs it said which node had not responded and times of each successful response. This would greatly help to identify systems that are the slow pokes or the ones that are potentially too busy to respond fast enough. Thanks! -- Corey Flowers Vice President, Onyx Point, Inc (410) 541-6699 [email protected] -- This account not approved for unencrypted proprietary information --
