Michael Kjellman created CASSANDRA-5102: -------------------------------------------
Summary: upgrading from 1.1.7 to 1.2.0 caused upgraded nodes to only know about other 1.2.0 nodes Key: CASSANDRA-5102 URL: https://issues.apache.org/jira/browse/CASSANDRA-5102 Project: Cassandra Issue Type: Bug Affects Versions: 1.2.0 Reporter: Michael Kjellman Priority: Blocker I upgraded as I have since 0.86 and things didn't go very smoothly. I did a nodetool drain to my 1.1.7 node and changed my puppet config to use the new merged config. When it came back up (without any errors in the log) a nodetool ring only showed itself. I upgraded another node and sure enough now nodetool ring showed two nodes. I tried resetting the local schema. The upgraded node happily grabbed the schema again but still only 1.2 nodes were visible in the ring to any upgraded nodes. "Interesting" Log Lines: INFO 14:43:41,997 Using saved token [42535295865117307932921825928971026436] .... WARN 23:04:03,361 No host ID found, created 5cef7f51-688d-46c3-9fe4-6c82bde4bb98 (Note: This should happen exa ctly once per node). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira