Thanks everyone. The issue was a missing firewall entry in the security
groups that prevented Cassandra from clustering.
So Alain, initially I was using the private IP. I went to irc and someone
had mentioned to use the public IP, although I wasnt doing multi region
clustering.
I should at some
Hi Richard,
I think you just can't use EC2Snitch with public IPs.
See
https://docs.datastax.com/en/cassandra/2.0/cassandra/architecture/architectureSnitchEC2_t.html
Precisely "Because private IPs are used, this snitch does not work across
multiple regions"
54.*.*.* looks like a public one.
Along the lines of what Ben and Bryan suggested, what are you using to
verify ports are open? If you do something like:
node1$ nc -zv node2 9042
node2$ nc -zv node1 9042
does it succeed from both nodes?
Does the first node 'know' that it is a seed? i.e. do you have first node
listed in its own
> On Wed, 3 Feb 2016 at 11:49 Richard L. Burton III
> wrote:
>
>>
>> Any suggestions on how to track down what might trigger this problem? I'm
>> not receiving any exceptions.
>>
>
You're not getting "Unable to gossip with any seeds" on the second node?
What does nodetool
I'm deploying 2 nodes at the moment using cassandra-dse on Amazon. I
configured it to use EC2Snitch and configured rackdc to use us-east with
rack "1".
The second node points to the first node as the seed e.g., "seeds":
["54.*.*.*"] and all of the ports are open.
Any suggestions on how to track
Check network connectivity. If you are using public addresses as the
broadcast, make sure you can telnet from one node to the other nodes public
address using the internode port.
Last time I looked into something like this, for some reason if you only
add a security group id to the allowed