[jira] [Updated] (CASSANDRA-5980) Allow cache keys-to-save to be dynamically set

["Chris Burroughs (JIRA)" <ji...@apache.org>]

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

Chris Burroughs updated CASSANDRA-5980:
---------------------------------------

    Attachment: j5980-a.txt

 * Adds getters/setters for *CacheKeysToSave
 * Dynamic mbean stuff, with scheduling patterned off of changing the cache save period
 * setcachekeystosave nodetool command
                
> Allow cache keys-to-save to be dynamically set
> ----------------------------------------------
>
>                 Key: CASSANDRA-5980
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5980
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Burroughs
>            Assignee: Chris Burroughs
>            Priority: Minor
>         Attachments: j5980-a.txt
>
>
> We have the option {key,row}_cache_keys_to_save so that operators can chose a balance between "can't handle load on cold start" and "takes too long to reboot".  However, this can currently only be set at startup.  This means that once it has been determined that X is a bad value for keys_to_save another badness inducing restart is required to change X.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira