You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/07/26 21:20:13 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13071297#comment-13071297 ]
Hudson commented on CASSANDRA-2082:
-----------------------------------
Integrated in Cassandra #975 (See [https://builds.apache.org/job/Cassandra/975/])
stop reading cache after max size-to-save is reached
patch by Chris Burroughs; reviewed by jbellis for CASSANDRA-2082
jbellis : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151211
Files :
* /cassandra/trunk/test/unit/org/apache/cassandra/db/RowCacheTest.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
> 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
> Fix For: 1.0
>
> Attachments: 0001-v1-Only-load-up-to-capacity-items-into-the-cache.patch, 0002-v1-unit-test-for-CASSANDRA-2082.patch
>
>
> 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