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

Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2015/03/18 21:04:39 UTC

[jira] [Updated] (CASSANDRA-5213) Failed to flush SSTable can cause commit log not to reply

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

Philip Thompson updated CASSANDRA-5213:
---------------------------------------
    Assignee: Yuki Morishita

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