You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Chris Burroughs (JIRA)" <ji...@apache.org> on 2011/07/22 19:41:00 UTC

[jira] [Assigned] (CASSANDRA-2082) Saved row cache continues to be read past max cache size

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

Chris Burroughs reassigned CASSANDRA-2082:
------------------------------------------

    Assignee: Chris Burroughs

> Saved row cache continues to be read past max cache size
> --------------------------------------------------------
>
>                 Key: CASSANDRA-2082
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2082
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.11
>            Reporter: Chris Burroughs
>            Assignee: Chris Burroughs
>            Priority: Minor
>
> Scenario:
>  - Node has a saved row cache of size n
>  - node OOMs
>  - Make row cache size = .5n to prevent OOM while we debug, restart node.
>  - n items are still read from the row cache, making startup take twice as long as needed.
> (This is intended as a straightforward bug, not as a hackish CASSANDRA-1966.)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira