cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patricio Echague (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2427) Heuristic or hard cap to prevent fragmented commit logs from bringing down the server
Date Mon, 13 Jun 2011 23:58:47 GMT

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

Patricio Echague updated CASSANDRA-2427:
----------------------------------------

    Attachment:     (was: CASSANDRA-2427-Jconsole-snapshot.tiff)

> 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-3-trunk-addNewSetting.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

        

Mime
View raw message