[
https://issues.apache.org/jira/browse/CASSANDRA-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980473#action_12980473
]
Jonathan Ellis commented on CASSANDRA-1970:
-------------------------------------------
it only restricts gossip, which isn't A Big Deal since it's so little traffic.
so how about this? we try to parse gossip packets in the current version; if
that fails, we parse in the old version. we don't accept commands from a node
until we have its version.
-----
hang on, don't we already have a per-message version field in the message
first-bytes-sent? i think it's reasonable to say "first int is always "magic,"
second is always bitfield containing version, streaming flag, etc. I'm willing
to commit to that indefinitely.
> 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.
