You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nick Bailey (JIRA)" <ji...@apache.org> on 2011/02/05 21:08:30 UTC

[jira] Commented: (CASSANDRA-2053) Make cache saving less contentious

    [ https://issues.apache.org/jira/browse/CASSANDRA-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991049#comment-12991049 ] 

Nick Bailey commented on CASSANDRA-2053:
----------------------------------------

+1

> 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.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