It also looks like you changed your topology by altering rack from r1 to
RAC1. Shouldn't effect this issue but something to get consistent.
On Thu, Mar 16, 2017 at 4:49 AM, George Sigletos
wrote:
> This was a network problem at our side after all which we fixed. Cassandra
> was blocking connecti
This was a network problem at our side after all which we fixed. Cassandra
was blocking connections between 192.168.xxx <-> 10.179.xxx on port 7000
On Wed, Mar 15, 2017 at 2:47 PM, Ryan Svihla wrote:
> I've actually changed the ip address quite a bit (gossip complains on
> startup and happily pi
I've actually changed the ip address quite a bit (gossip complains on
startup and happily picks up the new address), I think this maybe easier
such as..can those ip addresses route to one another ?
As in can the first node with 192.168.xx.xx hit the node with 10.179.xx.xx
on that interface?
On W
Cassandra uses the IP address for more or less everything. It's possible to
change it through some hackery however probably not a great idea. The nodes
system tables will still reference the old IP which is likely your problem
here.
On 14 March 2017 at 18:58, George Sigletos wrote:
> To give a c
To give a complete picture, my node has actually two network interfaces:
eth0 for 192.168.xx.xx and eth1 for 10.179.xx.xx
On Tue, Mar 14, 2017 at 7:46 PM, George Sigletos
wrote:
> Hello,
>
> I am trying to change the IP of a live node (I am not replacing a dead
> one).
>
> So I stop the service
