[
https://issues.apache.org/jira/browse/CASSANDRA-14759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619272#comment-16619272
]
Benedict commented on CASSANDRA-14759:
--------------------------------------
I thought I had already committed this as one of my other patches, but it seems
not. I hope you don't mind both being tagged reviewers, since you've been
reviewing my other TR follow ups, but shis bug is a proper Blocker for 4.0.
[PR|https://github.com/apache/cassandra/pull/270]
[CI|https://circleci.com/workflow-run/636b2eae-2d9e-4245-ad6b-462eab583f13]
I will follow up with some tests.
> Transient->Full movements mishandle consistency level upgrade
> -------------------------------------------------------------
>
> Key: CASSANDRA-14759
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14759
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Major
> Labels: Availability, correctness, transient-replication
> Fix For: 4.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
