cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10099) Improve concurrency in CompactionStrategyManager
Date Fri, 28 Aug 2015 02:17:45 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717925#comment-14717925
] 

Yuki Morishita commented on CASSANDRA-10099:
--------------------------------------------

Since both SSTable level and repaired status is stored in SSTable metadata, it seems possible
to complitely eliminate managing SSTables separately inside each compaction strategy. Maybe
we can just get (throw {{ColumnFamilyStore#select}}?) desired SSTables like uncompacting,
repaired or unrepaired, for certain SSTable level.
This way we can remove synchronized trace of SSTable addition / removal ({{INotificationConsumer}})
as well as {{CompactionStrategyManager}} itself.

> Improve concurrency in CompactionStrategyManager
> ------------------------------------------------
>
>                 Key: CASSANDRA-10099
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10099
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Yuki Morishita
>            Assignee: Yuki Morishita
>             Fix For: 3.x
>
>
> Continue discussion from CASSANDRA-9882.
> CompactionStrategyManager(WrappingCompactionStrategy for <3.0) tracks SSTable changes
mainly for separating repaired / unrepaired SSTables (+ LCS manages level).
> This is blocking operation, and can lead to block of flush etc. when determining next
background task takes longer.
> Explore the way to mitigate this concurrency issue.



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

Mime
View raw message