[
https://issues.apache.org/jira/browse/CASSANDRA-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980511#action_12980511
]
Gary Dusbabek commented on CASSANDRA-1970:
------------------------------------------
bq. Old nodes talking to new is no problem, it reads version off the header and
deserializes appropriately.
'it' meaning the version N node, yes.
bq. New node can't talk to old nodes initially because they read version and
have to drop it, they don't have that code.
Right.
bq. But as soon as new node knows the version of one of the old ones (i.e. as
soon as it gets a gossip message) it can update a Map of {inetaddress, version}
w/ the right value and we are good. No bounce required.
How wil N get a gossip message (a response) from N-1 if N-1 is rejecting every
attempt of N trying to introduce itself? Keep in mind that N-1 is dropping
those messages before they ever make it into the gossip code.
> Message version resolution
> --------------------------
>
> Key: CASSANDRA-1970
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1970
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.8
>
>
> When a new new node (version N) contacts an old node (version N-1) for the
> first time, the old node will not understand the message. One resolution
> mechanism would be for the old node to "bounce" the message back to the
> sender. The sender would then respond by translating the message to the
> appropriate version and resending it.
> For this to work, 0.7.1 will need to have the "bounce" feature.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
