cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Penick (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7816) Updated the "4.2.6. EVENT" section in the binary protocol specification
Date Fri, 22 Aug 2014 16:08:11 GMT


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:

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:
>             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

View raw message