[
https://issues.apache.org/jira/browse/CASSANDRA-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-2818:
----------------------------------------
Attachment: 2818.txt
In 0.7, we did actually add the node to the endpoint state map by calling
addSavedEndpoint. I removed this in CASSANDRA-2092, probably because it makes
the log message somewhat incorrect ("XXX has restarted, now UP again") but if
it was good enough for 0.7, I think it's good enough for 0.8. Note that even
without the disconnect 0.7->0.8 works, but the disconnect is an optimization.
Protection from DC/RACK NPEs is guaranteed by addSavedEndpoint initially
marking the node as down, so there's no reason to query the state information
(other things that utilize getNaturalEndpoints may NPE like nodetool ring, but
it's a short window to exploit and non-critical.) Patch to restore the
previous behavior to 0.8.
> A 0.8.1 version node can't join the ring made up of 0.8.0 nodes.
> ----------------------------------------------------------------
>
> Key: CASSANDRA-2818
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2818
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.1
> Reporter: Michael Allen
> Assignee: Brandon Williams
> Fix For: 0.7.7, 0.8.2
>
> Attachments: 2818-disconnect.txt, 2818.txt
>
>
> When a 0.8.1 node tries to join a 0.8.0 ring, we see an endless supply of
> these in system.log:
> INFO [Thread-4] 2011-06-23 21:14:04,149 IncomingTcpConnection.java (line 103)
> Received connection from newer protocol version. Ignorning message.
> and the node never joins the ring.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
