[ https://issues.apache.org/jira/browse/CASSANDRA-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2053: -------------------------------------- Attachment: 2053.txt Moves CacheWriter to a top-level class and runs it on the CompactionManager executor. Reads and writes udpated to use BRAF cache-non-polluting mode. > 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 > Fix For: 0.7.2 > > Attachments: 2053.txt > > > 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