[
https://issues.apache.org/jira/browse/CASSANDRA-7816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107017#comment-14107017
]
Michael Penick commented on CASSANDRA-7816:
-------------------------------------------
Yes, I've seen multiple UP/DOWN messages sent for the same event (I haven't
tried other events yet). At first, I thought it was a bug in my driver, but was
unable to determine the cause so I checked the java-driver:
https://github.com/datastax/java-driver/blob/2.0/driver-core/src/main/java/com/datastax/driver/core/Host.java#L217-L219
https://github.com/datastax/java-driver/blob/2.1/driver-core/src/main/java/com/datastax/driver/core/Host.java#L219-L221
I figured it might be a side effect of C*'s distributed design and the gossip
protocol so it didn't seem unreasonable. I haven't dug into the server-side
code yet to officially confirm why that's happening. I think it makes sense to
have a note in the protocol specification if this is determined to be part of
normal operating behavior.
> 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)
