[
https://issues.apache.org/jira/browse/CASSANDRA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866630#action_12866630
]
Ryan King commented on CASSANDRA-1079:
--------------------------------------
It appears the problem is that SSTableTracker's replace method calls
updateCacheSizes, which reads the cache settings from DatabaseDescriptor (which
doesn't get updated by the jmx command).
> 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
> Components: Core
> Affects Versions: 0.6
> Reporter: Ryan King
> Fix For: 0.6.2
>
>
> 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.
