@marksf Correct, the "key" icon will allow you to apply component level access policies to your process group with id "863928d5-12e7-...." Once "view the component" is granted the ID will be replaced with the actual process group name. "Modify the component" will allow the user to also add, modify and delete components within that process group. Thanks, Matt ... View more

Thanks for the config tip, really helpful. It eventually came up by the morning. I think the issue is that my Hadoop cluster is down and I have at least 50 connections to it. I imagine a few minute time out per connection, 3-6 connections each, that's a big chunk of time. ... View more

@Anshuman Ghosh No inconvenience at all. We just want to keep it as easy as possible for community members to find similar issues and solutions. I would have moved it myself if I couldhave. 🙂 ... View more

@Matt Clarke - I think I get it now. I was misunderstanding that within the Policy area I need to literally add their cert credentials. I was falsely assuming once I added a user, I would see those users as options to add to policies. It appears I must not only copy the users cert to the users area but also to all of the policies to which they should have access. I agree, I did not want to manually edit files. I was just previously confused how policies were getting applied. ... View more

@Matt Thanks, Matt this is something i was looking at. ... View more

@Benjamin Hopp What reason if NiFi giving in the nifi-app.log for the node disconnections? Rather then restarting the node that disconnects, did you try just clicking the reconnect icon in the cluster UI? Verify that your nodes do not have trouble communicating with each other. Makes there are no firewalls between the nodes affecting communications to the HTTP/HTTPS ports: nifi.web.http.host=nifi-ambari-08.openstacklocal nifi.web.http.port=8090 nifi.web.https.host=nifi-ambari-08.openstacklocal nifi.web.https.port=9091 or node communication port: nifi.cluster.node.address=nifi-ambari-08.openstacklocal nifi.cluster.node.protocol.port=9088 Make sure Both yo r nodes are properly configured to talk to ZK and neither has issues communicating with them: nifi.zookeeper.connect.string=nifi-ambari-09.openstacklocal:2181,nifi-ambari-07.openstacklocal:2181,nifi-ambari-08.openstacklocal:2181 nifi.zookeeper.connect.timeout=3 secs nifi.zookeeper.root.node=/nifi nifi.zookeeper.session.timeout=3 sec All of the above setting are in the nifi.properties file. Thanks, Matt ... View more

@Saurabh Verma How to change the JDK version for an existing cluster Re-run Ambari Server Setup. ambari-server setup At the prompt to change the JDK, Enter y. Do you want to change Oracle JDK [y/n] (n)? y At the prompt to choose a JDK, Enter 1 to change the JDK to v1.8. [1] - Oracle JDK 1.8 [2] - Oracle JDK 1.7 [3] - Custom JDK If you choose Oracle JDK 1.8 or Oracle JDK 1.7, the JDK you choose downloads and installs automatically on the Ambari Server host. This option requires that you have an internet connection. You must install this JDK on all hosts in the cluster to this same path. If you choose Custom JDK , verify or add the custom JDK path on all hosts in the cluster. Use this option if you want to use OpenJDK or do not have an internet connection (and have pre-installed the JDK on all hosts). After setup completes, you must restart each component for the new JDK to be used. Important You must also update your JCE security policy files on the Ambari Server and all hosts in the cluster to match the new JDK version. If you do not update the JCE to match the JDK, you may have issues starting services. Refer to the Ambari Security Guide for more information on Installing the JCE. Thanks, Matt ... View more

@Matt Thank you for your clarification. ... View more

@Joshua Adeleke There is obviously something else going on within your system that is affecting leader election. When you start you NiFi, do you see a leader election/Cluster coordinator count down timer running? Is your NiFi having trouble talking to your Zookeeper? Looks like you are having timeout issues talking to your zookeeper. I still don't understand why you are running your NiFi as a 1 node cluster if all you want is a single standalone instance of NiFi. A NiFi configured as a standalone instance does not need zookeeper and also does not perform election of cluster coordinator or primary node. Setting the following property in your nifi.properties and restarting will make you NiFi a truly standalone instance: nifi.cluster.is.node=false Matt ... View more

Thanks @Wynner! ... View more