[
https://issues.apache.org/jira/browse/NIFI-9010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens M Kofoed updated NIFI-9010:
--------------------------------
Description:
If I use the hostname (as the documentation says) for this property the load
balance port bind to localhost and the cluster can't load balancing.
If I use the IP address it binds to the IP address and it works.
nifi.cluster.load.balance.host=node.domain.net ->
result from netstat -l
tcp 0 0 localhost:6342 0.0.0.0:* LISTEN
nifi.cluster.load.balance.host=192.168.1.1 ->
result from netstat -l
tcp 0 0 192.168.10.1:6342 0.0.0.0:* LISTEN
was:
If I use the hostname (as the documentation says) for this property the load
balance port bind to localhost and the cluster can't load balancing.
If I use the IP address it bind to the IP address and it works.
nifi.cluster.load.balance.host=node.domain.net ->
result from netstat -l
tcp 0 0 localhost:6342 0.0.0.0:* LISTEN
nifi.cluster.load.balance.host=192.168.1.1 ->
result from netstat -l
tcp 0 0 192.168.10.1:6342 0.0.0.0:* LISTEN
> nifi.cluster.load.balance.host binds to localhost if specified with hostname
> ----------------------------------------------------------------------------
>
> Key: NIFI-9010
> URL: https://issues.apache.org/jira/browse/NIFI-9010
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.14.0
> Reporter: Jens M Kofoed
> Priority: Major
>
> If I use the hostname (as the documentation says) for this property the load
> balance port bind to localhost and the cluster can't load balancing.
> If I use the IP address it binds to the IP address and it works.
> nifi.cluster.load.balance.host=node.domain.net ->
> result from netstat -l
> tcp 0 0 localhost:6342 0.0.0.0:* LISTEN
> nifi.cluster.load.balance.host=192.168.1.1 ->
> result from netstat -l
> tcp 0 0 192.168.10.1:6342 0.0.0.0:* LISTEN
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
