You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2014/08/13 22:22:13 UTC
[jira] [Assigned] (CASSANDRA-7765) Don't use strict endpoint
selection for range movements where RF == node count
[ https://issues.apache.org/jira/browse/CASSANDRA-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe reassigned CASSANDRA-7765:
------------------------------------------
Assignee: Sam Tunnicliffe
> Don't use strict endpoint selection for range movements where RF == node count
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-7765
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7765
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Attachments: 7765.txt
>
>
> Post CASSANDRA-2434, we should skip strict endpoint selection for ranges where RF == the number of nodes in the cluster otherwise we hit the following assertion in {{RangeStreamer.getAllRangesWithStrictSourcesFor}}
> {code}
> if (oldEndpoints.size() == strat.getReplicationFactor())
> {
> oldEndpoints.removeAll(newEndpoints);
> assert oldEndpoints.size() == 1 : "Expected 1 endpoint but found " + oldEndpoints.size();
> }
> {code}
> I think this is a fairly niche case, plus there's a workaround in the {{-Dcassandra.consistent.rangemovement=false}} option.
--
This message was sent by Atlassian JIRA
(v6.2#6252)