cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8112) nodetool compactionhistory can allocate memory unbounded
Date Tue, 14 Oct 2014 13:05:33 GMT

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

T Jake Luciani commented on CASSANDRA-8112:
-------------------------------------------

Here's an option.  Once CASSANDRA-7402 goes in we can check the size of the result set and
by using a small page size we can stop loading after result set gets to say 1MB.

> nodetool compactionhistory can allocate memory unbounded
> --------------------------------------------------------
>
>                 Key: CASSANDRA-8112
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8112
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Priority: Minor
>             Fix For: 2.1.1
>
>
> nodetool compactionhistory keeps data for 1 week by default and creates a table from
the result set in memory.
> For many systems a week can generate 10's of thousands of compactions in this time (esp
with LCS) we should guard against this command allocating too much memory.



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

Mime
View raw message