9b rack1
>>
>> UN 192.168.187.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
37-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 with the rolling
with the rolling restart?
Paul Mena
Senior Application Administrator
WHOI - Information Services
508-289-3539
From: Shalom Sagges
Sent: Tuesday, November 26, 2019 12:59 AM
To: user@cassandra.apache.org
Subject: Re: Cassandra is not showing a node up hours after restart
Hi Paul,
From the gossipin
ossipinfo
>>>
>>> /192.168.187.121
>>>
>>> generation:1491825076
>>>
>>> heartbeat:2147483647
>>>
>>> STATUS:shutdown,true
>>>
>>> RACK:rack1
>>>
>>> NET_VERSION:8
>>>
>>
,true
>>
>> RACK:rack1
>>
>> NET_VERSION:8
>>
>> LOAD:5.78679987693E11
>>
>> RELEASE_VERSION:2.1.9
>>
>> DC:datacenter1
>>
>> SCHEMA:fd2dcb4b-ca62-30df-b8f2-d3fd774f2801
>>
>> HOST_ID:c99cf581-f4ae-4aa
185.121
>
> SEVERITY:0.0
>
>
>
>
>
> *Paul Mena*
>
> Senior Application Administrator
>
> WHOI - Information Services
>
> 508-289-3539
>
>
>
> *From:* Paul Mena
> *Sent:* Monday, November 25, 2019 9:29 AM
> *To:* user@cassandra.apache.org
> *Subjec
: Paul Mena
Sent: Monday, November 25, 2019 9:29 AM
To: user@cassandra.apache.org
Subject: RE: Cassandra is not showing a node up hours after restart
I’ve just discovered that NTP is not running on any of these Cassandra nodes,
and that the timestamps are all over the map. Could this be causing my
Services
508-289-3539
From: Inquistive allen
Sent: Monday, November 25, 2019 2:46 AM
To: user@cassandra.apache.org
Subject: Re: Cassandra is not showing a node up hours after restart
Hello team,
Just to add on to the discussion, one may run,
Nodetool disablebinary followed by a nodetool disablethrift
commands advisable? Are any other commands recommended either
>> before the shutdown or after the startup?
>>
>>
>> Thanks again!
>>
>>
>> Paul
>> --------------
>> *From:* Naman Gupta
>> *Sent:* Sunday, November 24, 2019 11:18:14 A
> Thanks again!
>
>
> Paul
> --
> *From:* Naman 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
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
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 wrote:
> 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
>
It sounds silly but sometimes restarting again the node which is showing
down from other nodes fix the issue. This looks like a gossip issue.
On Sun, Nov 24, 2019 at 7:19 AM Paul Mena wrote:
> I am in the process of doing a rolling restart on a 4-node cluster running
> Cassandra 2.1.9. I stopped
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
14 matches
Mail list logo
