[
https://issues.apache.org/jira/browse/CASSANDRA-16796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16796:
----------------------------------------
Test and Documentation Plan: new dtest added
Status: Patch Available (was: Open)
||branch||Circle CI||
|[16796-3.0|https://github.com/beobal/cassandra/tree/16796-3.0]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16796-3.0]|
|[16796-3.11|https://github.com/beobal/cassandra/tree/16796-3.11]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16796-3.11]|
|[16796-4.0|https://github.com/beobal/cassandra/tree/16796-4.0]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16796-4.0]|
|[16796-trunk|https://github.com/beobal/cassandra/tree/16796-trunk]|[circle|https://circleci.com/gh/beobal/cassandra?branch=16796-trunk]|
The 3.0/3.11 & 4.0/trunk patches are basically the same, so I've only kicked
off ci-c jobs for
[3.0|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/936]
and
[4.0|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/936]
> Clear pending ranges for a SHUTDOWN peer
> ----------------------------------------
>
> Key: CASSANDRA-16796
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16796
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Membership
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> If a node involved in a MOVE operation should fail, peers can sometimes
> maintain pending ranges even when it has left the ring and/or been replaced
> (in practice until the peer is next bounced). This in turn can lead to bogus
> unavailable responses to clients if a replica for the any of the pending
> ranges should go down.
> If the moving node crashes hard, a subsequent replacement will correctly fail
> as long as cassandra.consistent.rangemovement is set to true because the new
> node will learn the MOVING status from the remaining peers. A graceful
> shutdown, however, causes that status to be replaced with SHUTDOWN, but
> doesn't update TokenMetadata, so pending ranges remain for the down node,
> even after it has been removed from the ring.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
