You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/12/17 00:17:13 UTC

[jira] [Updated] (CASSANDRA-7533) Let MAX_OUTSTANDING_REPLAY_COUNT be configurable

     [ https://issues.apache.org/jira/browse/CASSANDRA-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-7533:
--------------------------------------
    Assignee: Branimir Lambov  (was: Yuki Morishita)

> Let MAX_OUTSTANDING_REPLAY_COUNT be configurable
> ------------------------------------------------
>
>                 Key: CASSANDRA-7533
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7533
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jeremiah Jordan
>            Assignee: Branimir Lambov
>            Priority: Minor
>             Fix For: 2.0.12
>
>
> There are some workloads where commit log replay will run into contention issues with multiple things updating the same partition.  Through some testing it was found that lowering CommitLogReplayer.java MAX_OUTSTANDING_REPLAY_COUNT can help with this issue.
> The calculations added in CASSANDRA-6655 are one such place things get bottlenecked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)