cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan King (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1079) Cache capacity settings done via nodetool get reset on memtable flushes
Date Wed, 12 May 2010 00:45:41 GMT

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

Ryan King commented on CASSANDRA-1079:
--------------------------------------

If we're not going to let the jmx-based setting live longer than one memtable, we should probably
remove the ability to set it that way. The current behavior is too surprising.

> Cache capacity settings done via nodetool get reset on memtable flushes
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-1079
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1079
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.6.1
>            Reporter: Ryan King
>
> In an experiment we set cache capacities via nodetool. The config file had the KeyCache
for this CF at 1000000, we set the RowCache to 10000000 via nodetool.
> The next time we flushed a memtable for that CF, the cache capacity settings got reverted
to what is in the conf file. We repeated the experiment with the same results.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message