87.122 634.04 GB 256 ?
bfa07f47-7e37-42b4-9c0b-024b3c02e93f rack1
UN 192.168.187.123 576.42 GB 256 ?
273df9f3-e496-4c65-a1f2-325ed288a992 rack1
UN 192.168.187.124 628.56 GB 256 ?
b8639cf1-5413-4ece-b882-2161bbb8a9c3 rack1
Is it inadvisable to continue
SION:8
LOAD:5.78679987693E11
RELEASE_VERSION:2.1.9
DC:datacenter1
SCHEMA:fd2dcb4b-ca62-30df-b8f2-d3fd774f2801
HOST_ID:c99cf581-f4ae-4aa9-ab37-1a114ab2429b
RPC_ADDRESS:192.168.185.121
SEVERITY:0.0
Paul Mena
Senior Application Administrator
WHOI - Information Services
508-289-3539
From
node004.intra.myorg.org | CHANGED | rc=0 >>
Mon Nov 25 14:07:20 UTC 2019
node003.intra.myorg.org | CHANGED | rc=0 >>
Mon Nov 25 13:57:06 UTC 2019
node001.intra.myorg.org | CHANGED | rc=0 >>
Mon Nov 25 14:07:22 UTC 2019
Paul Mena
Senior Application Administrator
WHOI - Information
man Gupta
Sent: Sunday, November 24, 2019 11:18:14 AM
To: user@cassandra.apache.org
Subject: Re: Cassandra is not showing a node up hours after restart
Did you change the name of datacenter or any other config changes before the
rolling restart?
On Sun, Nov 24, 2019 at 8:49 PM Paul Mena
mailto
I am in the process of doing a rolling restart on a 4-node cluster running
Cassandra 2.1.9. I stopped and started Cassandra on node 1 via "service
cassandra stop/start", and noted nothing unusual in either system.log or
cassandra.log. Doing a "nodetool status" from node 1 shows all four nodes up
