Created 11-22-2016 11:58 AM
I am trying to push data from NiFi instance (A) to another NiFi instance (B) with below configurations -
site to site properties in A
site to site properties in B
I configured RPG, could browse to the remote host using 'Go To' but couldn't see any ports in Remote Ports.
Created 11-22-2016 01:13 PM
Let's simplify the config to eliminate misconfiguration in other areas. If you want A to initiate the connection, you can remove those nifi.remote.* properties on the A side. Next, the port 8443 is not the best choice, as it often is used for https on non-privileged port. It's not even required now, as NiFi's s2s can tunnel over HTTP. Remove input.socket.port on the B side.
Finally, please share which URL you used in the RPG setup (the UI on the A side). The GoTo action simply opens a new browser window. What we are looking for is being able to Refresh the RPG and see ports after 20-30 seconds after initial setup.
Few more things to validate. I understand this is not a secured instance, so port access permissions aren't in play. Make sure, though, that instance B has input/output ports added the root top-level processing group, this is a requirements for the s2s.
Created 11-22-2016 01:13 PM
Let's simplify the config to eliminate misconfiguration in other areas. If you want A to initiate the connection, you can remove those nifi.remote.* properties on the A side. Next, the port 8443 is not the best choice, as it often is used for https on non-privileged port. It's not even required now, as NiFi's s2s can tunnel over HTTP. Remove input.socket.port on the B side.
Finally, please share which URL you used in the RPG setup (the UI on the A side). The GoTo action simply opens a new browser window. What we are looking for is being able to Refresh the RPG and see ports after 20-30 seconds after initial setup.
Few more things to validate. I understand this is not a secured instance, so port access permissions aren't in play. Make sure, though, that instance B has input/output ports added the root top-level processing group, this is a requirements for the s2s.
Created 11-22-2016 01:50 PM
Thanks for the quick answer @Andrew Grande.
I did the suggested changes but couldn't see the ports in RPG after initial setup.
Created 11-22-2016 04:43 PM
@spdvnz @Andrew Grande By input/output being in root Top level processing group what Andrew means is that it shouldn't be part of a process group. If you look at bottom left hand corner, your input port should be under NiFi Flow, not under a process group.
Also, site to site property in B should have nifi.remote.input.host=FQDN of B.
instance A of NiFi will initially talk to instance B of Nifi on public port ( how you access instance B UI ). Then instance B will reply with information available in nifi.remote.* properties. instance A, will then communicate with instance B on host and port specified in remote properties.
Can you please post a screenshot of your setup?
Created 11-22-2016 05:15 PM
Thanks for explaining the missing bits @Shishir Saxena, this is very valuable information.
I moved the input/output ports to root level processing group and I could transfer data from A to B.