@Maqbool as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. ... View more

Awesome! Glad everything is working. Just to follow with extra details so others that come across this post will benefit... There are a couple of key items to know when standing up NiFi behind a proxy. 1) NiFi is comprised of a number of web applications (web ui, web api, documentation, custom ui's, etc). So you'll need to set up your mapping to the root path. That way all context paths are pass through accordingly. For instance, if you only mapped the /nifi context path, the custom ui for Update Attributes will not work since it's available at /update-attribute-ui-<version>. 2) NiFi's rest api will generate uri's for each component on the graph. Since your coming through a proxy, you'll need to override certain elements of the uri's being generated. This is why your able to view the graph, but you cannot modify existing Processors. It's attempting to call back directly to your NiFi, not through your proxy. You can override the elements of the uri by adding the following HTTP headers when your proxy generates the HTTP request to the NiFi instance: X-ProxyScheme - the scheme to use to connect to your proxy (https in this case) X-ProxyHost - the host of your proxy X-ProxyPort - the port your proxy is listening on X-ProxyContextPath - the path you've configured to map to the NiFi instance ... View more

Hello @Matt Clarke, I started running the nodes in the cluster. Nodes are shown as 3/3 connected. But there is something wrong. When I add a processor in one of the nodes and then configure that processor, the URL redirects to its internal ip. For example, my public ip is : a.b.c.d and internal ip is a1.b1.c1.d1 then configuring processor redirects to : a1.b1.c1.d1:9999/nifi-api/processors/ID_of_Processor while it should be a.b.c.d/nifi-api/processors/ID_of_Processor ... View more

@Jatin Kheradiya try this way /usr/hdp/current/zookeeper-server/bin/zkCli.sh -server localhost:2181 -c create "/hello 1" "hvalue" /usr/hdp/current/zookeeper-server/bin/zkCli.sh -server localhost:2181 -c get "/hello 1" ... View more

@Jatin Kheradiya Couple things.... 1. zookeeper is not going to work very well with a single instance running. In order to achieve Quorum there should be an odd number of zookeeper servers (3, 5, 7, etc...) with 3 as a min to achieve quorum. 2. When NiFi nodes start they communicate with ZK to find out who the currently elected cluster coordinator is. They will all request to become the cluster coordinator and an election process will begin. Until this election completes, the nodes will not join the cluster. You should see election will end messages in the nifi-app.log when an election is on-going. There are two properties in the nifi.properties file that control the election process: nifi.cluster.flow.election.max.candidates= nifi.cluster.flow.election.max.wait.time=5 mins By default candidates is left blank which means the election will always run the full 5 minutes each time your NiFi cluster is restarted. To reduce how long the election takes to complete, set the candidates property to the number of nodes you have in your cluster. The election will complete once the configured number of candidates have checked in with zk or 5 minutes has passed. Thanks, Matt ... View more

Hello, Yes, i tried looking into it the way you told. It was some delimiter error in the query. Thanks @Matt Burgess ... View more

Yes i restarted NIFI. Still, it was not working. Then I cleared contents of content_repository and provenance_repository. It worked. ... View more