cassandra-commits mailing list archives

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

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

Dominik Keil commented on CASSANDRA-11301:
------------------------------------------

[~christianmovi]: I saw similar symptoms on that particular cluster and increasing the compaction
throughput seemed to help. Then again, the symptoms are elusive even on 2.2, where this is
confirmed and I did not create a thread dump. If it happens again I will do that (if I get
on it in time) and we'll see.

> 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