Aaron,
I added -Dcassandra.load_ring_state=false in the cassandra-env.sh and did a
rolling restart With one node in 1.2.3 version and 11 other nodes in
1.1.10, the 1.1.10 nodes saw 1.2.3 node but now the gossip on 1.2.3 only
sees itself.
Cheers,
-Arya
On Thu, Mar 28, 2013 at 1:02 PM, Arya
So all nodes are 1.2 and some are still being marked as down ?
I would try a rolling restart with -Dcassandra.load_ring_state=false added as a
JVM _OPT in cassandra-env.sh. There is no guarantee it will fix it, but it's a
simple thing to try.
Cheers
-
Aaron Morton
Freelance
I took Brandon's suggestion in CASSANDRA-5332 and upgraded to 1.1.10 before
upgrading to 1.2.2 but the issue with nodetool ring reporting machines as
down did not resolve.
On Fri, Mar 15, 2013 at 6:35 PM, Arya Goudarzi gouda...@gmail.com wrote:
Thank you very much Aaron. I recall from the logs
Thank you very much Aaron. I recall from the logs of this upgraded node to
1.2.2 reported seeing others as dead. Brandon suggested in
https://issues.apache.org/jira/browse/CASSANDRA-5332 that I should at least
upgrade from 1.1.7. So, I decided to try upgrading to 1.1.10 first before
upgrading to
Is this just a display bug in nodetool or this upgraded node really sees the
other ones as dead?
Is the 1.2.2 node which is see all the others as down processing requests ?
Is it showing the others as down in the log ?
I'm not really sure what's happening. But you can try starting the 1.2.2
despite my other issue having to do with the wrong version of cassandra,
this one still stands as described.
On Fri, Mar 8, 2013 at 10:24 PM, Arya Goudarzi gouda...@gmail.com wrote:
OK. I upgraded one node from 1.1.6 to 1.2.2 today. Despite some new
problems that I had and I posted them in a
OK. I upgraded one node from 1.1.6 to 1.2.2 today. Despite some new
problems that I had and I posted them in a separate email, this issue still
exists but now it is only on 1.2.2 node. This means that the nodes running
1.1.6 see all other nodes including 1.2.2 as Up. Here is the ring and
gossip
No I did not look at nodetool gossipinfo but from the ring on both
pre-upgrade and post upgrade nodes to 1.2.1, what I observed was the
described behavior.
On Sat, Feb 23, 2013 at 1:26 AM, Michael Kjellman
mkjell...@barracuda.comwrote:
This was a bug with 1.2.0 but resolved in 1.2.1. Did you
This was a bug with 1.2.0 but resolved in 1.2.1. Did you take a capture of
nodetool gossipinfo and nodetool ring by chance?
On Feb 23, 2013, at 12:26 AM, Arya Goudarzi gouda...@gmail.com wrote:
Hi C* users,
I just upgrade a 12 node test cluster from 1.1.6 to 1.2.1. What I noticed
from
