[
https://issues.apache.org/jira/browse/CASSANDRA-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599372#comment-13599372
]
Jonathan Ellis commented on CASSANDRA-5314:
-------------------------------------------
Hmm, this is tricky: as you say, we don't want to undo more-recent deletes, but
we also don't want to discard other rows in the batch, or even the row with low
gcgs, that may be necessary to preserve our Atomic Batch guarantees. I.e.:
replaying the batch may be incorrect, but not replaying it may also be
incorrect.
I think the only solution is to require that gcgs be greater than the batch
timeout we use.
> Replaying old batches can 'undo' deletes
> ----------------------------------------
>
> Key: CASSANDRA-5314
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5314
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Fix For: 1.2.3
>
>
> Batchlog manager does not subtract the time spent in the batchlog from hints'
> ttls and this may cause undoing deletes. The attached patch fixes it.
--
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
