cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5213) Failed to flush SSTable can cause commit log not to reply
Date Fri, 01 Feb 2013 00:07:13 GMT

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

Yuki Morishita updated CASSANDRA-5213:
--------------------------------------

    Description: 
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.

  was:
When flushing failed(e.g. out of disk space), that memtable was kept in memtablePendingFlush
and might trigger next flush inside MeteredFlusher.

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.

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