cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1970) Message version resolution
Date Wed, 12 Jan 2011 02:10:45 GMT


Jonathan Ellis commented on CASSANDRA-1970:

bq. We don't. 

So, given a ring of N-1, and version N joins:

Old nodes talking to new is no problem, it reads version off the header and deserializes appropriately.

New node can't talk to old nodes initially because they read version and have to drop it,
they don't have that code.

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.


> Message version resolution
> --------------------------
>                 Key: CASSANDRA-1970
>                 URL:
>             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.

View raw message