After restarting all the nodes, they all see each other. I'll try nodetool
gossipinfo if it happens again. Thanks.
From: Aaron Morton [mailto:aa...@thelastpickle.com]
Sent: Monday, December 23, 2013 10:19 PM
To: Cassandra User
Subject: Re: Issue upgrading from 1.2 to 2.0.3
If this is still
nodetool upgradesstables. We haven’t restarted since.
Is a restart required for each node?
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: Thursday, December 19, 2013 4:17 PM
To: user@cassandra.apache.org
Subject: Re: Issue upgrading from 1.2 to 2.0.3
On Thu, Dec 19, 2013 at 1:03
Hi,
We are in the process of upgrading 1.2 to 2.0.3. We have a four node cluster
and we're upgrading one node at a time. After upgrading two of the nodes, we
encountered a problem. We observed that if we run nodetool status on the 2.0.3
hosts, they would show 2 nodes down and 2 nodes up.
On Thu, Dec 19, 2013 at 1:03 PM, Parag Patel parag.pa...@fusionts.comwrote:
We are in the process of upgrading 1.2 to 2.0.3.
...
Please help as this will prevent us from pushing into production.
(as a general commentary :
for each node?
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: Thursday, December 19, 2013 4:17 PM
To: user@cassandra.apache.org
Subject: Re: Issue upgrading from 1.2 to 2.0.3
On Thu, Dec 19, 2013 at 1:03 PM, Parag Patel
parag.pa...@fusionts.commailto:parag.pa...@fusionts.com wrote:
We
