cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1970) Message version resolution
Date Tue, 11 Jan 2011 23:28:47 GMT

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

Gary Dusbabek commented on CASSANDRA-1970:
------------------------------------------

I don't think relying on gossip is reliable enough.  For instance, consider a N node joining
a cluster of N-1 nodes.  The first message sent will be a gossip message that likely won't
be understood.

> 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.


Mime
View raw message