@Gaurav Jain Ideally load-balancing would be handle by the systems pushing data to your NiFI. When that is not possible and you are forced to ingest all data to a single Node in your NiFi cluster, load-balancing must be handled via a dataflow implementation. Using a Remote Process Group (RPG) is the most common solution used to redistribute already ingested data across all node sin a cluster, but you can also use multiple PostHTTP processors (1 for every node in your cluster) and a single ListenHTTP processor to build a FlowFile distribution dataflow. See the following for more info... https://community.hortonworks.com/articles/16120/how-do-i-distribute-data-across-a-nifi-cluster.html Thanks, Matt ... View more

@Sunil Neurgaonkar It looks like you manually created your users.xml file rather then letting NiFi create it for you. Or you originally had teh initial admin identity configured as "cn=admin,dc=example, dc=org". Once the users.xml and authorizations.xml files are created the first time, changes to NiFi config files will not trigger any updates to these files. NiFi is trying to authorize your user "cn=admin,dc=example,dc=com"; however, this user does not exist in yoru users.xml file, so you are seeing the following error: 2017-05-0915:41:57,250 INFO [NiFiWebServer-17] o.a.n.w.a.c.AccessDeniedExceptionMapper cn=admin,dc=example,dc=com does not have permission to access the requested resource.ReturningForbidden response. A close look at your users.xml file provided above shows your user as: <useridentifier="99412284-acd9-3945-931b-362691f189ff"identity="cn=admin,dc=example,dc=org"/> Their is a mismatch between your ldap user DN and the DN of the user in the users.xml file. dc=com vs dc=org. You can simply manually correct this mismatch in the users.xml file and restart NiFi to fix your authorization issue. Thanks, Matt ... View more