[
https://issues.apache.org/jira/browse/CASSANDRA-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980500#action_12980500
]
Gary Dusbabek commented on CASSANDRA-1970:
------------------------------------------
bq. I don't get it. Why do we need any other hacks to find out version, given
this?
We don't. Getting the version is trivial. A version N-1 node will get that
value, realize that it doesn't match it's version and drop the message (or
resolve it--that's the point of this ticket). A version N node will get it and
translate it (the subject of another ticket).
I'm trying to point out your earlier suggestion (preserving the serialization
of gossip messages) goes a lot further than those first 8 bytes and locks us
into the serialization format of Message and Header, or introduces a lot of
special casing.
> 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.
