[
https://issues.apache.org/jira/browse/CASSANDRA-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490708#comment-13490708
]
Sylvain Lebresne commented on CASSANDRA-4679:
---------------------------------------------
As much as I'm happy to revert the part about starting the thrift/binary
protocol server first, I'd prefer some precision about "breaks all kind of
things". That is, does that break things only if people query the thrift
interface before MS and gossip are up (which would make sense, but in real life
doesn't seem like very likely to happen (which doesn't mean we shouldn't fix it
btw)), or does it break things in other cases?
> 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: 0001-4679.txt,
> 0002-Start-RPC-binary-protocol-before-gossip.txt,
> 0003-Remove-hardcoded-initServer-from-AntiEntropyServiceTes.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
