[CASSANDRA-14759] Transient->Full movements mishandle consistency level upgrade

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Legacy/Core
• Labels: Availability correctness transient-replication
• Severity: Normal
• Assignee: Benedict Elliott Smith
• Reporter: Benedict Elliott Smith

Authors

Benedict Elliott Smith

Reviewers

Alex Petrov, Ariel Weisberg

• Created: 18/Sep/18 15:14
• Updated: 15/May/20 08:01
• Resolved: 03/Oct/18 13:50

Description

While we need treat a transitioning node as ‘full’ for writes, so that it can safely begin serving full data requests once it has finished, we cannot maintain it in the ‘pending’ collection else we will also increase our consistency requirements by a node that doesn’t exist.

Issue Links

• is part of: CASSANDRA-14697 Transient Replication 4.0 pre-release followup work