cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Coli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4474) Respect five-minute flush moratorium after initial CL replay
Date Wed, 05 Sep 2012 21:23:08 GMT

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

Robert Coli commented on CASSANDRA-4474:
----------------------------------------

Though I don't completely agree with the approach (see CASSANDRA-1967), I appreciate the result.
Thank you for preventing my just-restarted node from compacting as a side effect of flush.
:)
                
> Respect five-minute flush moratorium after initial CL replay
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-4474
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4474
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Yuki Morishita
>            Priority: Minor
>              Labels: commitlog, compaction
>             Fix For: 1.1.5, 1.2.0
>
>         Attachments: 4474-1.1.txt
>
>
> As noted in CASSANDRA-1967, the post-replay flush can kick off compactions before the
five minute grace period introduced in CASSANDRA-3181 to avoid i/o contention while server
is warming up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message