Created 11-08-2016 04:35 PM
I am setting up 1 node cluster and reading about setting nifi.cluster.is.node. I am unsure what to set this to and how it impacts functionality. Insights appreicated.
Created 11-08-2016 04:37 PM
The "nifi.cluster.is.node" parameter is used to specify whether the NiFi installation is a standalone installation (false) or a node in a NiFi cluster (true). When set to true, things like ZK are required as "cluster" wide state management will not take affect and is stored in ZK. With true NiFi also requires a ZK for the NiFi Cluster (even if you have only 1 node) The NiFi node will send heartbeats to ZK and a primary node and cluster coordinator will be elected.
By setting to false, NiFi does not need a ZK for all those things above. [11:24 AM] Matthew Clarke: State management is only local as well.
You will get better performance out of a Standalone NIFi (false) then you will out of a 1 node cluster (true with only one node) because you reduce the overhead by not having the ZK piece.
Thanks,
Matt
Created 11-08-2016 04:37 PM
The "nifi.cluster.is.node" parameter is used to specify whether the NiFi installation is a standalone installation (false) or a node in a NiFi cluster (true). When set to true, things like ZK are required as "cluster" wide state management will not take affect and is stored in ZK. With true NiFi also requires a ZK for the NiFi Cluster (even if you have only 1 node) The NiFi node will send heartbeats to ZK and a primary node and cluster coordinator will be elected.
By setting to false, NiFi does not need a ZK for all those things above. [11:24 AM] Matthew Clarke: State management is only local as well.
You will get better performance out of a Standalone NIFi (false) then you will out of a 1 node cluster (true with only one node) because you reduce the overhead by not having the ZK piece.
Thanks,
Matt
Created 11-08-2016 04:38 PM
@mclark thanks for the clarification.