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 Wed, Mar 15, 2017 at 9:37 AM, kurt greaves <k...@instaclustr.com> wrote: > 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 <sigle...@textkernel.nl> wrote: > >> 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 <sigle...@textkernel.nl> >> 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 on my node (not a seed node), I change the IP from >>> 192.168.xx.xx to 10.179.xx.xx, and modify "listen_address" and >>> "rpc_address" in the cassandra.yaml, while I also set auto_bootstrap: >>> false. Then I restart but it fails to see the rest of the cluster: >>> >>> Datacenter: DC1 >>> =============== >>> Status=Up/Down >>> |/ State=Normal/Leaving/Joining/Moving >>> -- Address Load Tokens Owns Host >>> ID Rack >>> DN 192.168.xx.xx ? 256 ? >>> 241f3002-8f89-4433-a521-4fa4b070b704 r1 >>> UN 10.179.xx.xx 3.45 TB 256 ? >>> 3b07df3b-683b-4e2d-b307-3c48190c8f1c RAC1 >>> DN 192.168.xx.xx ? 256 ? >>> 19636f1e-9417-4354-8364-6617b8d3d20b r1 >>> DN 192.168.xx.xx ? 256 ? >>> 9c65c71c-f5dd-4267-af9e-a20881cf3d48 r1 >>> DN 192.168.xx.xx ? 256 ? >>> ee75219f-0f2c-4be0-bd6d-038315212728 r1 >>> >>> Am I doing anything wrong? Thanks in advance >>> >>> Kind regards, >>> George >>> >> >> > -- Thanks, Ryan Svihla
