Re: Request double-check on Ambari config logic (ES network_host)

: > > > > https://community.hortonworks.com/content/kbentry/24277/ > > > parameters-for-multi-homing.html > > > > that discusses these issues at some length, and clarifies why > they must > > > be > > > > separately configured. > &

Re: Request double-check on Ambari config logic (ES network_host)

tely configured. > > > > > > > > What do you-all think? > > > > > > > > Discussion item 2: While it’s fine to use 0.0.0.0 for the bind > address, > > > > it gives no guidance at all to the needed publish_host value.

Re: Request double-check on Ambari config logic (ES network_host)

ly add the square brackets and perhaps > > > substring quotes in python processing? Or should we say users need to > > > understand ES configuration, and tell them to put the list in square > > > brackets themselves, if they need a list en

Re: Request double-check on Ambari config logic (ES network_host)

“hadoop style” of >> > config parameter, and silently add the square brackets and perhaps >> > substring quotes in python processing? Or should we say users need to >> > understand ES configuration, and tell them to put the list in square >> > brackets themselves, if they ne

Re: Request double-check on Ambari config logic (ES network_host)

gt; > This event derives from this line of code: > > https://github.com/elastic/elasticsearch/blob/2.3/core/ > src/main/java/org/elasticsearch/action/support/master/ > TransportMasterNodeAction.java#L148 > > which suggests that a cluster action has been requested on a local

Re: Request double-check on Ambari config logic (ES network_host)

ldcard causes ES to > “listen” on all IP addresses, it > only *publishes* one, and on a multi-homed server it can be the wrong > one. I can’t be certain > this causes what you’re seeing, but it seems feasible. > > From: Otto Fowler <ottobackwa...@gmail.com> &g

Re: Request double-check on Ambari config logic (ES network_host)

rote: > The default will now be “0.0.0.0”, and not eth0. And this will work if > suggestions from various community members and a suggestion in the old 1.x > documentation for ES are correct. The 2.x documentation (we specify ES 2.3) > doesn’t mention “0.0.0.0”, but I t

Re: Request double-check on Ambari config logic (ES network_host)

ache.org" <dev@metron.apache.org>, "zeo...@gmail.com" <zeo...@gmail.com> Subject: Re: Request double-check on Ambari config logic (ES network_host) OK. I tried it using this method, and master ( adding [] ). In both cases, I can hit 9200 from other machines, but in bot

Re: Request double-check on Ambari config logic (ES network_host)

, 2017 at 11:27 AM To: "d...@metron.incubator.apache.org" <d...@metron.incubator.apache.org>, Matt Foley <mfo...@hortonworks.com>, "dev@metron.apache.org" < dev@metron.apache.org>, "zeo...@gmail.com" <zeo...@gmail.com> Subject: Re: Request do

Re: Request double-check on Ambari config logic (ES network_host)

dev@metron.apache.org>, "zeo...@gmail.com" <zeo...@gmail.com> Subject: Re: Request double-check on Ambari config logic (ES network_host) Are you saying that the defaults should work now? Or they should work, but I still need to change the interface from eth0? On May 2, 2017

Re: Request double-check on Ambari config logic (ES network_host)

Thanks! On May 2, 2017 at 14:58:37, Nick Allen (n...@nickallen.org) wrote: I don't know how to uninstall, but you can reinstall by passing the --force flag On Tue, May 2, 2017 at 2:33 PM, Otto Fowler wrote: > Do you know how to uninstall an mpack from the cli? > > >

Re: Request double-check on Ambari config logic (ES network_host)

ate: Tuesday, May 2, 2017 at 10:59 AM To: Matt Foley <mfo...@hortonworks.com>, "dev@metron.apache.org" <dev@metron.apache.org>, "d...@metron.incubator.apache.org" <d...@metron.incubator.apache.org>, Otto Fowler <ottobackwa...@gmail.com> Subject: Re:

Re: Request double-check on Ambari config logic (ES network_host)

As somebody who has systems that have globally-scoped addresses directly addressed onto servers, I would prefer using using "_local_", "_site_". Jon On Tue, May 2, 2017 at 1:36 PM Matt Foley wrote: > Hi Otto, > The basic change to use “0.0.0.0” as the default binding,

Re: Request double-check on Ambari config logic (ES network_host)

Are you working on this one? The JIRA doesn't look like it's currently assigned. Thanks, Jon On Mon, May 1, 2017 at 6:40 PM Matt Foley wrote: > Ah, I see I mis-read METRON-897, and Nick specifically says > "lo:ipv4","eth0:ipv4" did not work for him, but

Re: Request double-check on Ambari config logic (ES network_host)

Ah, I see I mis-read METRON-897, and Nick specifically says "lo:ipv4","eth0:ipv4" did not work for him, but ["_lo:ipv4_","_eth0:ipv4_"] did work. So I went back and dug a little deeper, and realized that in the environment where "lo:ipv4","eth0:ipv4" worked for me, I had modified the yaml.j2

Request double-check on Ambari config logic (ES network_host)

Hi, there have been widely varying statements about what needs to be in the Elasticsearch config parameter “network_host”. I think I may have a rationale for what works and what doesn’t, but I’d like your input or correction. I am focusing on what worked in terms of punctuation (quotes and