You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gary Dusbabek (JIRA)" <ji...@apache.org> on 2011/01/24 23:03:46 UTC

[jira] Issue Comment Edited: (CASSANDRA-1970) Message version resolution

    [ https://issues.apache.org/jira/browse/CASSANDRA-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985947#action_12985947 ] 

Gary Dusbabek edited comment on CASSANDRA-1970 at 1/24/11 5:02 PM:
-------------------------------------------------------------------

I like the bouncing approach because it is simple and less invasive than modifying gossip. attached as v1.

      was (Author: gdusbabek):
    I like the bouncing approach because it is simple and less invasive than modifying gossip.
  
> 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.7.1
>
>         Attachments: 1970.txt, v1-0001-bounce-messages-from-newer-versions.txt, v2-0001-ignore-messages-from-newer-versions-keep-track-of-node.txt
>
>
> 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.