[ https://issues.apache.org/jira/browse/CASSANDRA-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2053: -------------------------------------- Remaining Estimate: 4h Original Estimate: 4h > Make cache saving less contentious > ---------------------------------- > > Key: CASSANDRA-2053 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2053 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 0.7.0 > Reporter: Nick Bailey > Assignee: Jonathan Ellis > Fix For: 0.7.1 > > Attachments: 2053.txt > > Original Estimate: 4h > Remaining Estimate: 4h > > The current default for saving key caches is every hour. Additionally the > default timeout for flushing memtables is every hour. I've seen situations > where both of these occuring at the same time every hour causes enough > pressure on the node to have it drop messages and other nodes mark it dead. > This happens across the cluster and results in flapping. > We should do something to spread this out. Perhaps staggering cache > saves/flushes that occur due to timeouts. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira