cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11412) Many sstablescanners opened during repair
Date Fri, 01 Apr 2016 08:36:25 GMT

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

Marcus Eriksson updated CASSANDRA-11412:
----------------------------------------
    Fix Version/s: 3.x
                   3.0.x
           Status: Patch Available  (was: Open)

patch [here|https://github.com/krummas/cassandra/tree/marcuse/11412] - it opens the scanners
with the Collection<Range<Token>> method instead of one scanner per range per
sstable. For LCS it opens one scanner per level and one scanner per sstable in L0

tests:
http://cassci.datastax.com/view/Dev/view/krummas/job/krummas-marcuse-11412-dtest/
http://cassci.datastax.com/view/Dev/view/krummas/job/krummas-marcuse-11412-testall/

> Many sstablescanners opened during repair
> -----------------------------------------
>
>                 Key: CASSANDRA-11412
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11412
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 3.0.x, 3.x
>
>
> Since CASSANDRA-5220 we open [one sstablescanner per range per sstable|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/db/compaction/CompactionStrategyManager.java#L374].
If compaction gets behind and you are running vnodes with 256 tokens and RF3, this could become
a problem (ie, {{768 * number of sstables}} scanners)
> We could probably refactor this similar to the way we handle scanners with LCS - only
open the scanner once we need it



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message