[
https://issues.apache.org/jira/browse/CASSANDRA-7816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107039#comment-14107039
]
Sylvain Lebresne commented on CASSANDRA-7816:
---------------------------------------------
bq. Yes, I've seen multiple UP/DOWN messages sent for the same event
I guess my question is, do you have a simple way to reproduce that? Or is that
something you saw once or twice completely randomly during your tests.
The reason I added this kind of comments in the java driver is that I didn't
wanted to dive into the gossip code to make extra sure that it was impossible
to get a duplicate event even on a race, and I didn't wanted people to get
surprised and blame the driver if that happened, but I don't think there is a
good reason this could happen "easily". So wondered if you have easy step to
reproduce, because if that's the case we can have a quick look at fixing it.
Note that I'm good adding specifying in the doc that there is no strong
guarantee on this anyway, it's just that you ticket makes me wonder if there
isn't something we can easily fix server side.
> Updated the "4.2.6. EVENT" section in the binary protocol specification
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-7816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7816
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation & website
> Reporter: Michael Penick
> Priority: Trivial
> Attachments: trunk-7816.txt
>
>
> Added "MOVED_NODE" as a possible type of topology change and also specified
> that it is possible to receive the same event multiple times.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
