[
https://issues.apache.org/jira/browse/CASSANDRA-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569441#comment-14569441
]
Benedict commented on CASSANDRA-9388:
-------------------------------------
That was erroneously left present. Originally I had intended to collect the
memtables to discard at once (thereby only issuing one barrier for all of
them). Since typically there isn't more than one, and the efficiency isn't
dramatic, I opted to just immediately reclaim as that improved clarity.
I've pushed an updated version
[here|https://github.com/belliottsmith/cassandra/tree/9388-2.1] (with
equivalent branches for each mainline)
> Truncate can (in theory) lead to corrupt responses to client or segfault
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-9388
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9388
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Minor
> Fix For: 2.1.x
>
> Attachments: 9388.txt
>
>
> Noticed this while searching for another problem. I don't have a unit test
> exhibiting it, as it would be non-trivial to add (needs a high rate burn test
> of writes, reads, truncates and non-snapshotted CFs). We can perhaps file a
> follow-up ticket to address that, however the kitchen sink tests will
> hopefully cover this ground.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
