EC2 discovery is not working for me

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

EC2 discovery is not working for me

Marty
I'm getting the following:
[2011-09-08 21:14:17,793][INFO ][node                     ] [Pyre]
{elasticsearch/0.17.6}[8746]: initializing ...
[2011-09-08 21:14:17,808][INFO ][plugins                  ] [Pyre]
loaded [cloud-aws], sites []
[2011-09-08 21:14:20,633][INFO ][node                     ] [Pyre]
{elasticsearch/0.17.6}[8746]: initialized
[2011-09-08 21:14:20,633][INFO ][node                     ] [Pyre]
{elasticsearch/0.17.6}[8746]: starting ...
[2011-09-08 21:14:20,722][INFO ][transport                ] [Pyre]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.38.111.22:9300]}
[2011-09-08 21:14:26,632][WARN ][transport.netty          ] [Pyre]
Message not fully read (response) for [6] handler
future(org.elasticsearch.discovery.zen.membership.MembershipAction
$1@397b6074), error [false], resetting
[2011-09-08 21:14:26,632][INFO ][discovery.ec2            ] [Pyre]
failed to send join request to master [[Coral][9H4lLBnlQoGTs34jhIPKug]
[inet[/10.84.129.100:9300]]], reason
[org.elasticsearch.transport.RemoteTransportException: Failed to
deserialize response of type
[org.elasticsearch.discovery.zen.membership.MembershipAction
$JoinResponse];
org.elasticsearch.transport.TransportSerializationException: Failed to
deserialize response of type
[org.elasticsearch.discovery.zen.membership.MembershipAction
$JoinResponse]; java.io.IOException: Expected handle header, got
[110]]

I verified though the console that I can create keys in the s3
bucket.  Any guesses what operation is failing?

Thanks!
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery is not working for me

Paul Loy
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}

What's your config? Looks like you're not specifying a host?

On Fri, Sep 9, 2011 at 5:15 AM, Marty <[hidden email]> wrote:
I'm getting the following:
[2011-09-08 21:14:17,793][INFO ][node                     ] [Pyre]
{elasticsearch/0.17.6}[8746]: initializing ...
[2011-09-08 21:14:17,808][INFO ][plugins                  ] [Pyre]
loaded [cloud-aws], sites []
[2011-09-08 21:14:20,633][INFO ][node                     ] [Pyre]
{elasticsearch/0.17.6}[8746]: initialized
[2011-09-08 21:14:20,633][INFO ][node                     ] [Pyre]
{elasticsearch/0.17.6}[8746]: starting ...
[2011-09-08 21:14:20,722][INFO ][transport                ] [Pyre]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.38.111.22:9300]}
[2011-09-08 21:14:26,632][WARN ][transport.netty          ] [Pyre]
Message not fully read (response) for [6] handler
future(org.elasticsearch.discovery.zen.membership.MembershipAction
$1@397b6074), error [false], resetting
[2011-09-08 21:14:26,632][INFO ][discovery.ec2            ] [Pyre]
failed to send join request to master [[Coral][9H4lLBnlQoGTs34jhIPKug]
[inet[/10.84.129.100:9300]]], reason
[org.elasticsearch.transport.RemoteTransportException: Failed to
deserialize response of type
[org.elasticsearch.discovery.zen.membership.MembershipAction
$JoinResponse];
org.elasticsearch.transport.TransportSerializationException: Failed to
deserialize response of type
[org.elasticsearch.discovery.zen.membership.MembershipAction
$JoinResponse]; java.io.IOException: Expected handle header, got
[110]]

I verified though the console that I can create keys in the s3
bucket.  Any guesses what operation is failing?

Thanks!



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery is not working for me

James Cook
We sometimes use 0.0.0.0 as our network.host value on EC2, so I don't think that is the problem.

It looks like the master node in the cluster was discovered, and an attempt was made to communicate with the master. An error occurred while trying to "deserialize response of type". Are you running the same version of ES on both nodes?


Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery is not working for me

Marty
Interesting.  I'm running 3 ES unicast (manual IP address) ES boxes
running 0.16.2 and I'm trying to bring up a new cluster so it can
replace the old one.  I think you're right.  It's finding an old
master.  Sounds like I should bump the old boxes up to the same
version as the new cluster.

I'll give that a try.

Thanks!

On Sep 9, 6:39 am, James Cook <[hidden email]> wrote:
> We sometimes use 0.0.0.0 as our network.host value on EC2, so I don't think
> that is the problem.
>
> It looks like the master node in the cluster was discovered, and an attempt
> was made to communicate with the master. An error occurred while trying to
> "deserialize response of type". Are you running the same version of ES on
> both nodes?