cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9533) Make batch commitlog mode easier to tune
Date Wed, 22 Jul 2015 22:36:05 GMT

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

Benedict commented on CASSANDRA-9533:
-------------------------------------

I suspect that is commit log segment recycling, as opposed to batch commit log mode. 

If you look, performance is at parity until several hundred megabytes have been written, at
which point a memtable will have flushed and commit log segments will be made available for
reuse.

> Make batch commitlog mode easier to tune
> ----------------------------------------
>
>                 Key: CASSANDRA-9533
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9533
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Benedict
>             Fix For: 3.x
>
>
> As discussed in CASSANDRA-9504, 2.1 changed commitlog_sync_batch_window_in_ms from a
maximum time to wait between fsync to the minimum time, so one must be very careful to keep
it small enough that most writers aren't kept waiting.



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

Mime
View raw message