> - broadcast_address is set to the instance's public address
You only need this if you have a multi region setup.
> I’ve gisted the results here:
> https://gist.github.com/skyebook/be5ee75a000a1e6d65d0
This error
TRACE [HANDSHAKE-/NODE_1_PUBLIC_IP] 2013-11-18 06:57:13,984
OutboundTcpConnect
Hi there,
I’m bringing this thread back as its something that I thought was solved and is
apparently not fixed on my end.
To recap, I’m having trouble getting a node to join a cluster. Configuration
seems all right using the EC2MultiRegionSnitch but new nodes are unable to
handshake with seed
> INFO 05:03:49,015 Cannot handshake version with /aa.bb.cc.dd
> INFO 05:03:49,017 Handshaking version with /aa.bb.cc.dd
If you can turn up logging to TRACE for
org.apache.cassandra.net.OutboundTcpConnection it will include the full error.
> The two addresses that it is unable to handshake wit
Hi Aaron, thanks for the clarification.
As might be expected, having the broadcast_address fixed hasn't fixed anything.
What I did find after writing my last email is that output.log is littered
with these:
INFO 05:03:49,015 Cannot handshake version with /aa.bb.cc.dd
INFO 05:03:49,017 Handsh
> I am curious, though, how any of this worked in the first place spread
> across three AZ's without that being set?
boradcast_address is only needed when you are going cross region (IIRC it's the
EC2MultiRegionSnitch) that sets it.
As rob said, make sure the seed list includes on of the other
Thank you, both Michael and Robert for your suggestions. I actually saw 5760,
but we were running on 2.0.0, which it seems like this was fixed in.
That said, I noticed that my Chef scripts were failing to set the
broadcast_address correctly, which I'm guessing is the cause of the problem,
fixi
Check your security groups to be sure you have appropriate access.
If in a VPC check both IN and OUT; if using ACLs check those.
On Wed, Sep 25, 2013 at 3:41 PM, Skye Book wrote:
> Hi all,
>
> I have a three node cluster using the EC2 Multi-Region Snitch currently
> operating only in US-EAST.
On Wed, Sep 25, 2013 at 12:41 PM, Skye Book wrote:
> I have a three node cluster using the EC2 Multi-Region Snitch currently
> operating only in US-EAST. On having a node go down this morning, I
> started a new node with an identical configuration, except for the seed
> list, the listen address
Hi all,
I have a three node cluster using the EC2 Multi-Region Snitch currently
operating only in US-EAST. On having a node go down this morning, I started a
new node with an identical configuration, except for the seed list, the listen
address and the rpc address. The new node comes up and c
