cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7765) Don't use strict endpoint selection for range movements where RF == node count
Date Fri, 04 Dec 2015 20:39:11 GMT

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

Sam Tunnicliffe updated CASSANDRA-7765:
---------------------------------------
    Component/s: Coordination

> 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
>          Components: Coordination
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 2.1.0
>
>         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.3.4#6332)

Mime
View raw message