You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/06/24 15:53:49 UTC
[jira] [Commented] (CASSANDRA-2818) A 0.8.1 version node can't join
the ring made up of 0.8.0 nodes.
[ https://issues.apache.org/jira/browse/CASSANDRA-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054454#comment-13054454 ]
Jonathan Ellis commented on CASSANDRA-2818:
-------------------------------------------
Not sure what's going on. Here's what's supposed to happen:
If new node N is contacted first by old node M, N records the version of M and generates messages at that version. M never knows that N is actually newer.
If M is contacted first, we expect to see the above message a few times, but M adds N to its gossip list after the first time. Once N gets a gossip from M, it will know to use M's version when creating messages.
I don't see anything obviously wrong with this code. :(
> 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.8.1
> Reporter: Michael Allen
> Fix For: 0.8.1
>
>
> 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