[ https://issues.apache.org/jira/browse/CASSANDRA-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Hermes updated CASSANDRA-2100: ---------------------------------- Attachment: 2100-3.txt Slight surprise in testing due to 2172 changes, but tests correctly (save period is updated at runtime for both JMX and schema migrations (both client and non-client mode)). > 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.3 > > Attachments: 2100-2.txt, 2100-3.txt, 2100.txt > > Original Estimate: 2h > Remaining Estimate: 2h > > 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