You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by Laurens Vets <la...@daemon.be> on 2017/05/11 18:51:58 UTC
Elasticsearch: network.publish_host needed it seems
Environment:
- 2 VMs, each with 2 ip addresses (interfaces enp0s3 & enp0s8) called
node1 and node3
- ES master on node1, data node on node3
- CentOS 7
For some reason, elasticsearch uses the ip attached to enp0s3 as it's
publish address. Due to the way my test environment is set up, this will
not work. ES should use the ip address of enp0s8. However, we've been
trying to debug this over irc and nothing seems to work in Ambari except
setting network.publish_host manually in elasticsearch.yml on node1 &
node3 and restarting 'manually'. Unfortunately, this setting will be
gone from both hosts when I restart via Ambari.
We've tried the following in Ambari:
- network.host: 0.0.0.0 => Wrong ip used (enp0s3).
- network.host: "_lo:ipv4_","_enp0s8:ipv4_" => This blows up Java
- network.host: "_lo:ipv4","_enp0s8:ipv4" or ["_lo:ipv4","_enp0s8:ipv4"]
=> Unknown host exception in Java.
Any idea how I can add network.publish_host to Ambari so that it doesn't
get removed when I restart the services via Ambari? Or what setting I
need to use for network.host?
Re: Elasticsearch: network.publish_host needed it seems
Posted by Laurens Vets <la...@daemon.be>.
Hey David,
"[_local_,_site_]" didn't work, but you put me on the right path. It
seems that "[_enp0s8_]" works! Thanks!
> Have you tried [_local_,_site_]? If that doesn't work, perhaps give the
> publish address for enp0s8. Be sure to set that on the network_host
> field
> in the Elasticsearch config and leave network_publish_host empty.
>
> -D...
>
>
> On Thu, May 11, 2017 at 2:51 PM, Laurens Vets <la...@daemon.be>
> wrote:
>
>> Environment:
>> - 2 VMs, each with 2 ip addresses (interfaces enp0s3 & enp0s8) called
>> node1 and node3
>> - ES master on node1, data node on node3
>> - CentOS 7
>>
>> For some reason, elasticsearch uses the ip attached to enp0s3 as it's
>> publish address. Due to the way my test environment is set up, this
>> will
>> not work. ES should use the ip address of enp0s8. However, we've been
>> trying to debug this over irc and nothing seems to work in Ambari
>> except
>> setting network.publish_host manually in elasticsearch.yml on node1 &
>> node3
>> and restarting 'manually'. Unfortunately, this setting will be gone
>> from
>> both hosts when I restart via Ambari.
>>
>> We've tried the following in Ambari:
>> - network.host: 0.0.0.0 => Wrong ip used (enp0s3).
>> - network.host: "_lo:ipv4_","_enp0s8:ipv4_" => This blows up Java
>> - network.host: "_lo:ipv4","_enp0s8:ipv4" or
>> ["_lo:ipv4","_enp0s8:ipv4"]
>> => Unknown host exception in Java.
>>
>> Any idea how I can add network.publish_host to Ambari so that it
>> doesn't
>> get removed when I restart the services via Ambari? Or what setting I
>> need
>> to use for network.host?
>>
Re: Elasticsearch: network.publish_host needed it seems
Posted by David Lyle <dl...@gmail.com>.
Hi Laurens,
Have you tried [_local_,_site_]? If that doesn't work, perhaps give the
publish address for enp0s8. Be sure to set that on the network_host field
in the Elasticsearch config and leave network_publish_host empty.
-D...
On Thu, May 11, 2017 at 2:51 PM, Laurens Vets <la...@daemon.be> wrote:
> Environment:
> - 2 VMs, each with 2 ip addresses (interfaces enp0s3 & enp0s8) called
> node1 and node3
> - ES master on node1, data node on node3
> - CentOS 7
>
> For some reason, elasticsearch uses the ip attached to enp0s3 as it's
> publish address. Due to the way my test environment is set up, this will
> not work. ES should use the ip address of enp0s8. However, we've been
> trying to debug this over irc and nothing seems to work in Ambari except
> setting network.publish_host manually in elasticsearch.yml on node1 & node3
> and restarting 'manually'. Unfortunately, this setting will be gone from
> both hosts when I restart via Ambari.
>
> We've tried the following in Ambari:
> - network.host: 0.0.0.0 => Wrong ip used (enp0s3).
> - network.host: "_lo:ipv4_","_enp0s8:ipv4_" => This blows up Java
> - network.host: "_lo:ipv4","_enp0s8:ipv4" or ["_lo:ipv4","_enp0s8:ipv4"]
> => Unknown host exception in Java.
>
> Any idea how I can add network.publish_host to Ambari so that it doesn't
> get removed when I restart the services via Ambari? Or what setting I need
> to use for network.host?
>