Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <20006426.164211295896244303.JavaMail.jira@thor>
Date: Mon, 24 Jan 2011 14:10:44 -0500 (EST)
From: "Gary Dusbabek (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1970) Message version resolution
In-Reply-To: <21305114.297191294784146474.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Dusbabek updated CASSANDRA-1970:
-------------------------------------

    Fix Version/s:     (was: 0.8)
                   0.7.1

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