cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Bossa (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-6125) Race condition in Gossip propagation
Date Tue, 01 Oct 2013 19:01:27 GMT
Sergio Bossa created CASSANDRA-6125:

             Summary: Race condition in Gossip propagation
                 Key: CASSANDRA-6125
             Project: Cassandra
          Issue Type: Bug
            Reporter: Sergio Bossa

Gossip propagation has a race when concurrent VersionedValues are created and submitted/propagated,
causing some updates to be lost, even if happening on different ApplicationStatuses.
That's what happens basically:
1) A new VersionedValue V1 is created with version X.
2) A new VersionedValue V2 is created with version Y = X + 1.
3) V2 is added to the endpoint state map and propagated.
4) Nodes register Y as max version seen.
5) At this point, V1 is added to the endpoint state map and propagated too.
6) V1 version is X < Y, so nodes do not ask for his value after digests.

A possible solution would be to propagate/track per-ApplicationStatus versions, possibly encoding
them to avoid network overhead.

This message was sent by Atlassian JIRA

View raw message