[
https://issues.apache.org/jira/browse/CASSANDRA-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-609:
-------------------------------------
Attachment: 609-2.patch
I was thinking that the final table.flush is a "normal" flush so that should
take care of it. But thinking about it more we do have a corner case of "the
last write in the log happened to exactly hit the threshold and triggered a
no-discard flush, so the final flush saw a clean memtable and did nothing."
Patch 2 (applies on top of first) addresses this. (Most of the patch is
converting CL to a true singleton so replay has access to the normal context
operations w/o ugly hacks.)
> Easy to OOM on log replay since memtable limits are ignored
> -----------------------------------------------------------
>
> Key: CASSANDRA-609
> URL: https://issues.apache.org/jira/browse/CASSANDRA-609
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.5
>
> Attachments: 609-2.patch, 609.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
