Paresh, The RPG should communicate with the target instance everything 30 seconds in the background to discover available ports. A couple of possibilities
1) Which version of NiFi are you running? In 0.4.1 we addressed an issue that caused the RPGs to not refresh as often as it should [1]. You should be able to confirm this is the case by manually refreshing your browser. 2) Are your instances secured? If so, the target instances need to have the accounts for the referencing NiFi approved and access to specific ports need to be granted. Once this is completed, you should only see the available ports you have access to. Matt [1] https://issues.apache.org/jira/browse/NIFI-1309?focusedCommentId=15064696&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15064696 On Fri, Jan 29, 2016 at 3:05 PM, Paresh Shah <[email protected]> wrote: > We are in the process of automating the pipeline deloyment across multiple > clusters. In our scenario there are two different clusters with their own > pipelines. And the ports are open on both the machines. > > When I’m creating the RPG on the sending cluster it failed saying that the > destination is not reachable. Then after 3/4 minutes I was able to > successfully hook up the RPG. This 3/4 minutes is it configurable somewhere. > > Paresh > ________________________________ > The information contained in this transmission may contain privileged and > confidential information. It is intended only for the use of the person(s) > named above. If you are not the intended recipient, you are hereby notified > that any review, dissemination, distribution or duplication of this > communication is strictly prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all copies > of the original message. > ________________________________ >
