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

Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2012/08/20 21:43:37 UTC

[jira] [Commented] (CASSANDRA-4474) Respect five-minute flush moratorium after initial CL replay

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

Yuki Morishita commented on CASSANDRA-4474:
-------------------------------------------

Jonathan,

Do you mean flush after commit log recovery should not trigger compaction so that 5-min grace compaction can pick that up? I'm thinking to disable compaction until commit log is fully replayed and after that, enable compaction and schedule 5-min one shot compaction.
                
> 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
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira