For 0.16.2 and below I think you may have to specify the tcp.host as the
private ipv4 address. This is what the ec2 plugin will add to zen so if tcp
has not bound to that address they will not find each other.
For 0.16.2 and below I think you may have to specify the tcp.host as the private ipv4 address. This is what the ec2 plugin will add to zen so if tcp has not bound to that address they will not find each other.
what do you see in the logs?
On Wed, Jun 22, 2011 at 3:24 PM, Karl karl.baum@gmail.com wrote:
I am attempting to get ec2 discovery working but thus far i think i
have been unsuccessful. My config file looks like:
For 0.16.2 and below I think you may have to specify the tcp.host as the
private ipv4 address. This is what the ec2 plugin will add to zen so if tcp
has not bound to that address they will not find each other.
On Wed, Jun 22, 2011 at 4:26 PM, Karl Baum karl.baum@gmail.com wrote:
Hi Paul. I am a bit confused because my elasticsearch does not supply any ip addresses.. just my ec2 account information.
I am running into a bit of trouble with my logs. Somehow i have disabled logging to a file in an attempt to turn trace on for discovery.
For 0.16.2 and below I think you may have to specify the tcp.host as the private ipv4 address. This is what the ec2 plugin will add to zen so if tcp has not bound to that address they will not find each other.
what do you see in the logs?
On Wed, Jun 22, 2011 at 3:24 PM, Karl karl.baum@gmail.com wrote:
I am attempting to get ec2 discovery working but thus far i think i
have been unsuccessful. My config file looks like:
it is a pain in 0.16.2 that you have to have specific config per node.
However, in the next release of Elasticsearch you will get special values
that will query EC2 meta-data to obtain the ip address, such as _
ec2:privateIp_
You do already get benefits of using the ec2 plugin. You get Zen + the
initial hosts set for you from EC2 instance information.
Hmmm.. if that is the case why not just use zen discovery?
Thx!
On Jun 23, 2011, at 7:00 AM, Paul Loy wrote:
That's what I mean. You need to specify, in your config, the private ipv4
address as the tcp host. I think that's the publish_host here: Elastic — The Search AI Company | Elastic
For 0.16.2 and below I think you may have to specify the tcp.host as the
private ipv4 address. This is what the ec2 plugin will add to zen so if tcp
has not bound to that address they will not find each other.
it is a pain in 0.16.2 that you have to have specific config per node.
However, in the next release of Elasticsearch you will get special values
that will query EC2 meta-data to obtain the ip address, such as _
ec2:privateIp_
You do already get benefits of using the ec2 plugin. You get Zen + the
initial hosts set for you from EC2 instance information.
Hmmm.. if that is the case why not just use zen discovery?
Thx!
On Jun 23, 2011, at 7:00 AM, Paul Loy wrote:
That's what I mean. You need to specify, in your config, the private ipv4
address as the tcp host. I think that's the publish_host here: Elastic — The Search AI Company | Elastic
For 0.16.2 and below I think you may have to specify the tcp.host as the
private ipv4 address. This is what the ec2 plugin will add to zen so if tcp
has not bound to that address they will not find each other.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.