Site to Site Properties
These properties govern how this instance of NiFi communicates with remote instances of NiFi when Remote Process Groups are configured in the dataflow. Remote Process Groups can choose transport protocol from RAW and HTTP. Properties named with nifi.remote.input.socket.* are RAW transport protocol specific. Similarly, nifi.remote.input.http.* are HTTP transport protocol specific properties.
|
Property |
Description |
|
nifi.remote.input.host |
The host name that will be given out to clients to connect to this NiFi
instance for Site-to-Site communication. By default, it is the value from
InetAddress.getLocalHost().getHostName(). On UNIX-like operating systems, this
is typically the output from the |
|
nifi.remote.input.secure |
This indicates whether communication between this instance of NiFi and
remote NiFi instances should be secure. By default, it is set to
|
|
nifi.remote.input.socket.port |
The remote input socket port for Site-to-Site communication. By default, it is blank, but it must have a value in order to use RAW socket as transport protocol for Site-to-Site. |
|
nifi.remote.input.http.enabled |
Specifies whether HTTP Site-to-Site should be enabled on this host. By
default, it is set to Whether a Site-to-Site client uses HTTP or HTTPS is determined by
|
|
nifi.remote.input.http.transaction.ttl |
Specifies how long a transaction can stay alive on the server. By default,
it is set to If a Site-to-Site client hasn't proceeded to the next action after this period of time, the transaction is discarded from the remote NiFi instance. For example, when a client creates a transaction but doesn't send or receive flow files, or when a client sends or receives flow files but doesn't confirm that transaction. |
|
nifi.remote.contents.cache.expiration |
Specifies how long NiFi should cache information about a remote NiFi instance when communicating via Site-to-Site. By default, NiFi will cache the responses from the remote system for has many instances of Remote Process Groups. |