@Iyappan Gopalakrishnan Adding new users to a secured NiFI 0.x / HDF 1.x version of NiFi can be done directly via the NIFi UI. I am assuming you have already secured your NiFi and manually added the initial admin to the authorized-users.xml file. Adding new users is pretty easy. Simply have the new user attempt to access the https web address for your nifi 0.7 install. After authenticating successfully (Done via client certs, ldap, etc), they will see a screen telling them they are not authorized for access and giving them the opportunity to request access. Once they request access, the "Admin" user who does have access to the UI will need need to go into the users UI by clicking on the below Icon which can be found in the upper right corner of the NiFi UI: From within that UI you will see all existing users and any pending authorization users. Simply click on the pencil icon to the right of any pending users to authorize them for 1 or more of the available user roles (Administrator, Dataflow Manger, Read Only, or Provenance). The administration-guide included with your install can give you more details on each of the roles and what privileges each grants to the users. Thanks, Matt ... View more

@mayki wogno The reported error message is a little misleading, but the key to your issue is reported in the "Caused by" portion of the stack trace: Causedby: org.apache.nifi.controller.UninheritableFlowException:ProposedAuthorizerisnot inheritable by the flow controller because of Authorizer differences:ProposedAuthorizationsdonot match current Authorizations Verify that the authorizers.xml file on your new node matches the configuration on your other existing connected nodes. Remove the users.xml and authorizations.xml files from your new node as well be restarting. The new Node should be getting these files from the cluster when it joins. If you continue to see the same error message on restart, try copying the users.xml and authorizations.xml files from one of your existing connected nodes to this new node and restart again. Thanks, Matt ... View more

@ambud.sharma Each Node in a NiFi cluster runs its own copy of the dataflow and works on its own set of FlowFiles. Node A for example is unaware of the existence of Node B. NiFi does persist all FlowFiles (attributes and content) in to local repositories on each node in the cluster. That is why is is important to make these repo fault tolerant (For example using RAID 10 Disk for your repos). Should a node go down, as long as you have access to those repos and copy of the flow.xml.gz, you can recover your dataflow where it left off, even if that means spinning up a new NiFi and pointing it at those existing repos. NiFi comes with no automated built in process for this. While Nodes at this current time are not aware of other nodes or the data the currently have queued, This is a roadmap item for a future version of NiFi. At this time the HA Data plane stuff has not been committed to any particular release to the best of my knowledge. Thanks, Matt ... View more