cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Anastasyev (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-6087) Node OOMs on commit log replay when starting up
Date Tue, 24 Sep 2013 13:39:04 GMT

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

Oleg Anastasyev updated CASSANDRA-6087:
---------------------------------------

    Attachment: CassandraDaemon.txt
    
> Node OOMs on commit log replay when starting up
> -----------------------------------------------
>
>                 Key: CASSANDRA-6087
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6087
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Oleg Anastasyev
>         Attachments: CassandraDaemon.txt
>
>
> After some activity on batchlogs and hints and CFs restarted nodes without finished draining.
On startup it OOMs. 
> Investigating it found, that memtables occupied all available RAM, because MeteredFlusher
is started later in setup code, so memtables cannot flush. 
> Fixed by starting metered flusher before commit log replay starts

--
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