[
https://issues.apache.org/jira/browse/CASSANDRA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927484#action_12927484
]
Mike Bulman commented on CASSANDRA-1670:
----------------------------------------
INFO 15:48:22,176 Joining: getting load information
INFO 15:48:22,177 Sleeping 90000 ms to wait for load information...
DEBUG 15:48:23,053 GC for ParNew: 12 ms, 15822112 reclaimed leaving 15102720
used; max is 1268449280
DEBUG 15:48:23,166 attempting to connect to /184.106.231.n0
INFO 15:48:23,553 Node /184.106.231.n0 is now part of the cluster
DEBUG 15:48:23,554 Resetting pool for /184.106.231.n0
DEBUG 15:48:23,559 Node /184.106.231.n0 state normal, token
104110673354167092736227093944218730763
DEBUG 15:48:23,559 New node /184.106.231.n0 at token
104110673354167092736227093944218730763
DEBUG 15:48:23,559 clearing cached endpoints
DEBUG 15:48:24,167 attempting to connect to /184.106.231.n0
DEBUG 15:48:24,169 Disseminating load info ...
INFO 15:48:24,554 InetAddress /184.106.231.n0 is now UP
INFO 15:48:24,554 Started hinted handoff for endpoint /184.106.231.n0
INFO 15:48:24,557 Finished hinted handoff of 0 rows to endpoint /184.106.231.n0
DEBUG 15:49:24,169 Disseminating load info ...
DEBUG 15:49:39,106 GC for ParNew: 16 ms, 16111512 reclaimed leaving 85537648
used; max is 1268449280
DEBUG 15:49:52,177 ... got load info
INFO 15:49:52,177 Joining: getting bootstrap token
DEBUG 15:49:52,183 attempting to connect to /184.106.231.n0
DEBUG 15:49:52,191 Processing response on a callback from 270@/184.106.231.n0
INFO 15:49:52,192 New token will be 19040081623932476870383442086276677899 to
assume load from /184.106.231.n0
DEBUG 15:49:52,193 clearing cached endpoints
DEBUG 15:49:52,194 Will try to load mx4j now, if it's in the classpath
INFO 15:49:52,194 Will not load MX4J, mx4j-tools.jar is not in the classpath
INFO 15:49:52,220 Binding thrift service to /0.0.0.0:9160
INFO 15:49:52,222 Using TFramedTransport with a max frame size of 15728640
bytes.
INFO 15:49:52,226 Listening for thrift clients...
DEBUG 15:50:24,170 Disseminating load info ...
DEBUG 15:50:52,247 DECOMMISSIONING
DEBUG 15:51:24,170 Disseminating load info ...
DEBUG 15:52:24,171 Disseminating load info ...
>From n0:
r...@ripcord:/usr/src/cassandra/branches/cassandra-0.7# bin/nodetool -h
184.106.231.n0 ring
Address Status State Load Token
104110673354167092736227093944218730763
184.106.228.n1 Up Normal 5.3 KB
19040081623932476870383442086276677899
184.106.231.n0 Up Normal 10.27 KB
104110673354167092736227093944218730763
r...@ripcord:/usr/src/cassandra/branches/cassandra-0.7# bin/nodetool -h
184.106.228.n1 decommission
<TRACE FROM MY PREVIOUS COMMENT>
r...@ripcord:/usr/src/cassandra/branches/cassandra-0.7# bin/nodetool -h
184.106.231.n0 ring
Address Status State Load Token
104110673354167092736227093944218730763
184.106.228.n1 Up Normal 5.3 KB
19040081623932476870383442086276677899
184.106.231.n0 Up Normal 10.27 KB
104110673354167092736227093944218730763
> cannot move a node
> ------------------
>
> Key: CASSANDRA-1670
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1670
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.6.6
> Environment: RAX
> Reporter: Matthew F. Dennis
> Assignee: Gary Dusbabek
> Fix For: 0.6.7, 0.7.0
>
> Attachments: 1670-0.6.txt,
> v1-0001-code-that-tidied-Gossiper.justRemovedEndpoints_-was-no.txt
>
>
> two node cluster (node0, node1). node0 is listed as the only seed on both
> nodes. Listen addresses explicitly set to an IP on both nodes. No initial
> token, no autobootstrap (but see below). Bring up the ring. Everything is
> fine on both nodes.
> decom node1. verify decom completed correctly by reading the logs on both
> nodes. rm all data/logs on node1. bring node1 up again.
> One of two things happen:
> * node0 thinks it is in a ring by itself, node1 thinks both nodes are in the
> ring.
> * both node0 and node1 think they are in rings by themselves
> If you restart node0 after decom, it appears to work normally.
> Similar issues seem to present if you kill node1 (either when
> autobootstrapping before it completes or after it is in the ring) and
> removetoken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
