[
https://issues.apache.org/jira/browse/CASSANDRA-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Hermes updated CASSANDRA-2100:
----------------------------------
Attachment: 2100.txt
row/key cache save period in seconds now config-able at runtime via JMX (not
just migrations).
On either migration or JMX-change path, the scheduling has been broken out. It
first cancels the previous scheduled task (but will not interrupt currently
saving caches) then schedules a new task with the correct frequency.
> Restart required to change cache_save_period
> --------------------------------------------
>
> Key: CASSANDRA-2100
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2100
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Nick Bailey
> Assignee: Jon Hermes
> Priority: Minor
> Fix For: 0.7.2
>
> Attachments: 2100.txt
>
>
> The cache_save_period is set in the schema for each column family. However
> this value is only checked when a node starts up so changing this value isn't
> really dynamic.
> We should actually change this when the schema changes instead of having to
> restart.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
