@Anishkumar Valsalam You have encountered the following: https://issues.apache.org/jira/browse/NIFI-4363 You can get around this issue by editing the following script on every NiFi node in your cluster: /var/lib/ambari-agent/cache/common-services/NIFI/1.0.0/package/files/nifi-toolkit-1.2.0.3.0.1.0-43/bin/encrypt-config.sh Near the bottom of the script you will find this line: "${JAVA}" -cp "${CLASSPATH}" -Xms128m -Xmx256m org.apache.nifi.properties.ConfigEncryptionTool "$@" Edit it so that it now says: "${JAVA}" -cp "${CLASSPATH}" -Xms512m -Xmx1024m org.apache.nifi.properties.ConfigEncryptionTool "$@" Then go back to Ambari and start your NiFi service. Thank you, Matt ... View more

@dhieru singh Only processor properties that explicitly state that they support NiFi Expression Language will allow you to set variables. The "Port" property requires that a hard coded integer value is supplied. There is work being done to expand the capability of the NiFi variable registry. That work will expand what processor properties support EL. I recommend opening an Apache Jira requesting that the "Port" properties add support for NiFi expression language. Until then, there is no workaround. The value must be supplied directly in the processor. Thanks, Matt ... View more

@Andre Labbe 1. NiFi is designed to prevent changes while a node is disconnected. Each node runs its own copy of the flow.xml.gz. When a node is disconnected, the cluster coordinator has not means to determine the state of components on that disconnected node. If changes were allowed to be made, that node would be unable to automatically rejoin the cluster without manual intervention to bring them back in sync. To regain control of the canvas you can access the cluster UI and drop the disconnected node from the cluster. Keep in mind that if you want to later rejoin that node, you will need to make sure the flow.xml.gz, users.xml (if used when NiFi is secured), and authorizations.xml (if used when NiFi is secured) are all in-sync with what is currently be used in cluster (you can copy these from other active cluster node). *** Be mindful that if a change you made removed a connection that contained data on your disconnected node, that data will be lost on startup once you replace the flow.xml.gz. If Nifi cannot find the connection to place the queued data it is lost. 2. If you set a Processor component to execute on "Primary node", it dose not run. What component and how do you know it did not run? If have not see this happen before. Processors that use no cluster friendly protocols should be run on Primary Node only to prevent data duplication as you noted above. If you are consuming a lot of data using one of these protocols, ti is suggested you use the List/Fetch (example: listSFTP/FetchSFTP) processors along with NiFi's Site-To-Site (S2S) capability to redistribute the listed FlowFiles to all nodes in your cluster before the Fetch. Also note that you need an odd number of Zookeeper nodes in order to have Quorum. (3 minimum). Using the embedded zookeeper means you lose that ZK node anytime you restart that NiFi instance. I don't recommend using embedded ZK in production. Thanks, Matt ... View more