You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yifan Cai (Jira)" <ji...@apache.org> on 2021/09/10 16:09:00 UTC

[jira] [Updated] (CASSANDRA-16945) Multiple full sources can be select unexpectedly for bootstrap streaming

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

Yifan Cai updated CASSANDRA-16945:
----------------------------------
     Bug Category: Parent values: Availability(12983)Level 1 values: Process Crash(12992)
       Complexity: Low Hanging Fruit
    Discovered By: User Report
         Severity: Low
           Status: Open  (was: Triage Needed)

>  Multiple full sources can be select unexpectedly for bootstrap streaming
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-16945
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16945
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Consistency/Bootstrap and Decommission
>            Reporter: Yifan Cai
>            Assignee: Yifan Cai
>            Priority: Normal
>
> With CASSANDRA-14404, the RangeStreamer selects all endpoints as sources when using strict consistency and RF > endpoints count. In such case, the bootstrapping node is almost guaranteed to fail in the validation later. 
> It is a change of behavior. Before the patch, in such case (i.e., higher RF) the bootstrapping node just pick one endpoint as source, since consistent range movement cannot be established. I'd propose to restore the old behavior.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org