cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11301) Non-obsoleting compaction operations over compressed files can impose rate limit on normal reads
Date Thu, 03 Mar 2016 20:20:18 GMT

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

Benedict commented on CASSANDRA-11301:
--------------------------------------

I did not look too closely as I don't work actively on the project at the moment, however
I don't think 2.1 should be affected.

> Non-obsoleting compaction operations over compressed files can impose rate limit on normal
reads
> ------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11301
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11301
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Benedict
>             Fix For: 2.2.6
>
>
> Broken by CASSANDRA-9240; the rate limiting reader passes the ICompressedFile interface
to its parent, which uses this to attach an "owner" - which means the reader gets recycled
on close, i.e. pooled, for normal use. If the compaction were to replace the sstable there
would be no problem, which is presumably why this hasn't been encountered frequently. However
validation compactions on long lived sstables would permit these rate limited readers to accumulate.



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

Mime
View raw message