[jira] Resolved: (CASSANDRA-760) Optimize pending ranges.

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis resolved CASSANDRA-760.
--------------------------------------

    Resolution: Not A Problem

Discussed w/ Gary on irc -- since pending ranges only need to be updated on token movement, this is not an important thing to optimize.

> Optimize pending ranges.
> ------------------------
>
>                 Key: CASSANDRA-760
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-760
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Gary Dusbabek
>            Priority: Minor
>
> After 620, pending ranges are calculated on a per-table basis.  This isn't optimal, as the pending ranges of some tables will be subsets of pending ranges for other tables with the same replication strategy but a greater replication factor.
> This can be optimized.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.