Remote instance of NiFi is not configured to allow RAW Socket site-to-site communications

Site to Site communication can be done using below 2 methods
1. HTTP
2. RAW

HTTP method uses NiFi API to communicate information between NiFi instances using the HTTP protocol. The second method for Site to Site communication is RAW protocol which uses a dedicated port between the NiFi instances to do the communication. Using RAW protocol eases the pressure from the NiFi UI as dedicated port will be used

The most command error we saw during the setup of raw site to site protocol is Remote instance of NiFi is not configured to allow RAW Socket site-to-site communications To fix this error we will need to set below properties

# Site to Site properties
 nifi.remote.input.host=<FQDN of Host>              <-- Set to resolveable FQDN by all Nodes
 nifi.remote.input.secure=false                     <-- Set to True on if NiFi is running HTTPS
 nifi.remote.input.socket.port=<Port used for S2S)  <-- Needs to be set to support Raw/enable S2S
 nifi.remote.input.http.enabled=true                <-- Set if you want to support HTTP transport
 nifi.remote.input.http.transaction.ttl=30 sec 

After doing above settings restart NiFi instance

Leave a Reply