[
https://issues.apache.org/jira/browse/CASSANDRA-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466824#comment-13466824
]
Sylvain Lebresne commented on CASSANDRA-4679:
---------------------------------------------
I suppose we can, yes. Though I suspect there may be races so that some queries
(I'm thinking schema altering ones though honestly I haven't checked) might
trigger assertion errors or related if gossip isn't started. Probably worth
checking though. Maybe in a separate ticket however since it's not directly
related (clients will have a to handle the case where after a NEW_NODE the node
cannot be joined anyway).
> 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
