You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremiah Jordan (JIRA)" <ji...@apache.org> on 2015/03/23 17:04:11 UTC
[jira] [Assigned] (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 ]
Jeremiah Jordan reassigned CASSANDRA-7533:
------------------------------------------
Assignee: Jeremiah Jordan (was: Branimir Lambov)
> 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: Jeremiah Jordan
> Priority: Minor
> Fix For: 2.0.14
>
>
> 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)