[jira] [Issue Comment Edited] (CASSANDRA-2427) Heuristic or hard cap to prevent fragmented commit logs from bringing down the server

["Patricio Echague (JIRA)" <ji...@apache.org>]

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

Patricio Echague edited comment on CASSANDRA-2427 at 6/14/11 6:10 PM:
----------------------------------------------------------------------

Make CommitLog implement MBean
Executor no longer implement MBean
Wire the logic for removing the oldest segment
CommitLogTotalSize is exposed in bytes now


      was (Author: patricioe):
    Make CommitLog implement MBean
Executor no longer implement MBean
Wire the logic for removing the oldest segment

  
> Heuristic or hard cap to prevent fragmented commit logs from bringing down the server
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2427
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2427
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benjamin Coverston
>            Assignee: Patricio Echague
>              Labels: commitlog, hardening
>             Fix For: 1.0
>
>         Attachments: CASSANDRA-2427-4-trunk.txt, CASSANDRA-2427-Jconsole-snapshot.tiff, CASSANDRA-2427-trunk.txt
>
>
> Widely divergent write rates on column families can cause the commit log segments to fragment. In some cases we have seen the commit log partition overrun.
> One solution here would be to create a heuristic for segment fragmentation to trigger a flush (commit log segments/memtable) or simply track the free disk space and force a global flush when the disk gets to 80% capacity.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira