[ 
https://issues.apache.org/jira/browse/CASSANDRA-20659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Capwell updated CASSANDRA-20659:
--------------------------------------
          Fix Version/s: 4.0.18
                         4.1.10
                         5.0.5
                         5.1
                             (was: 5.x)
                             (was: 4.1.x)
                             (was: 5.0.x)
          Since Version: 0.3
    Source Control Link: 
https://github.com/apache/cassandra/commit/c736d22cf855d0981bb514fce5cb3a149b8c2f43
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

> Gossip doesn't converge due to race condition when updating EndpointStates 
> multiple fields
> ------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-20659
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20659
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Cluster/Gossip
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: 4.0.18, 4.1.10, 5.0.5, 5.1
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The issue seen is during shrinks or token moves the cluster gets into a state 
> where some of the nodes never converge and see the latest STATUS state for 
> the changed peers.
> In testing this it was found that:
> 1) org.apache.cassandra.gms.Gossiper#applyStateLocally expects to run in a 
> single thread, so doesn't take any locks
> 2) org.apache.cassandra.gms.Gossiper.GossipTask runs in another thread and 
> uses a taskLock to avoid sending partial state
> 3) org.apache.cassandra.gms.Gossiper#applyNewStates gets called when the 
> generation matches, and tries to apply the state sequentially.
> The theory (and test) is
> 1) localState.setHeartBeatState(remoteState.getHeartBeatState()); runs
> 2) something (gossip or paxos) read the state
> 3) localState.addApplicationStates(updatedStates); updates the state
> the "something" in step 2 sends around the heartbeat which cause others to 
> see a higher max version, so the delta logic won't see the mutations done in 
> step 3



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to