cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-5213) Failed to flush SSTable can cause commit log not to reply
Date Mon, 13 Jul 2015 04:37:05 GMT

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

Jonathan Ellis resolved CASSANDRA-5213.
---------------------------------------
    Resolution: Not A Problem

MeteredFlusher is gone in 2.1+

> Failed to flush SSTable can cause commit log not to reply
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-5213
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5213
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Yuki Morishita
>            Assignee: Yuki Morishita
>            Priority: Minor
>
> When flushing failed(e.g. out of disk space), that memtable was kept in memtablePendingFlush
and might trigger next flush inside MeteredFlusher since it would be always calculated in
countFlushingBytes.
> If that next flush succeeded(e.g. this time it fit on disk), ReplayPosition was recorded
at that point, and would cause commit log not to replay for the data that was not flushed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message