I don't think it is cloud at all, and I am no newcomer to sysadmin (though
am relative new to AWS cloud). The mistake is clearly mine, but also
clearly easy to make -- so I assume a lot of other people must make it too.
But the logs don't provide any guidance. Or is this another mistake I make,
whi
These issues are more cloud specific then they are cassandra specific.
Cloud executives tell me in white papers that cloud is awesome and you
can fire all your sysadmins and network people and save money.
This is what happens when you believe cloud executives and their white
papers, you spend 10+
I think it is actually more of a problem that there were no error messages
or other indication of what went wrong in the setup where the nodes
couldn't contact. Should I file issue report on this? Clearly Cassandra
must have tried to contact some IP on port 7000 and failed. Why didn't it
log? That
This is something that I found while using the multi-region snitch -
it uses public IPs for communication. See the original ticket here:
https://issues.apache.org/jira/browse/CASSANDRA-2452. It'd be nice if
it used the private IPs to communicate with nodes that are in the same
region as itself, but
OK. I got it. I realized that storage_port wasn't actually open between the
nodes, because it is using the public IP. (I did find this information in
the docs, after looking more... it is in section on "Types of snitches." It
explains everything I found by try and error.)
After opening this port 7
No, it doesn't works, same thing: both nodes seems to just exist solo and I
have 2 single-node clusters :-( OK, so now I am confused, and hope list
will help me out. To understand what wrong, I think I need to know what
happens in node bootstrap, and in node join ring. Who does node
communicate, on
Hi,
I've checked all things Alain suggested and set up a fresh 2-node cluster,
and I still get the same result: each node lists itself as only one.
This time I made the following changes:
- I set listen_address to the public DNS name. Internally, AWS's DNS
will map this to the 10.x IP, so
