cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7533) Let MAX_OUTSTANDING_REPLAY_COUNT be configurable
Date Mon, 23 Mar 2015 16:13:11 GMT

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

Jeremiah Jordan updated CASSANDRA-7533:
---------------------------------------
    Attachment: 0001-CASSANDRA-7533.txt

Have had a couple more people hitting this, so I think we should put something in for it.

Here is a simple fix to add -Dcassandra.commitlog_max_outstanding_replay_count=X to allow
a user to change it from the default.

> 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
>
>         Attachments: 0001-CASSANDRA-7533.txt
>
>
> 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)

Mime
View raw message