Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 2 Oct 2012 00:56:07 +1100 (NCT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1563846808.147785.1349099767925.JavaMail.jiratomcat@arcas>
In-Reply-To: <734315422.92378.1347976987629.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CASSANDRA-4679) Fix binary protocol NEW_NODE
 event
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-4679:
-------------------------------------------

We can always change that ordering.  Maybe we should.
                
> Fix binary protocol NEW_NODE event
> ----------------------------------
>
>                 Key: CASSANDRA-4679
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4679
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2.0 beta 2
>
>         Attachments: 4679.txt
>
>
> As discussed on CASSANDRA-4480, the NEW_NODE/REMOVED_NODE of the binary protocol are not correctly fired (NEW_NODE is fired on node UP basically). This ticket is to fix that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira