You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2018/09/18 16:02:00 UTC
[jira] [Comment Edited] (CASSANDRA-14759) Transient->Full movements
mishandle consistency level upgrade
[ https://issues.apache.org/jira/browse/CASSANDRA-14759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619334#comment-16619334 ]
Benedict edited comment on CASSANDRA-14759 at 9/18/18 4:01 PM:
---------------------------------------------------------------
bq. use of an enum instead of true/false might be a hair easier to follow for that API
-Agreed, I had that thought before too. I'll update the API.-
Actually, the method is no longer used, so I'll remove it (for now)
was (Author: benedict):
bq. use of an enum instead of true/false might be a hair easier to follow for that API
Agreed, I had that thought before too. I'll update the API.
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org