I can readily reproduce the bug, and filed a JIRA ticket:
https://issues.apache.org/jira/browse/CASSANDRA-9194
I’m posting for posterity
On Apr 13, 2015, at 11:59 AM, Robert Wille
mailto:rwi...@fold3.com>> wrote:
Unfortunately, I’ve switched email systems and don’t have my emails from that
ti
Unfortunately, I’ve switched email systems and don’t have my emails from that
time period. I did not file a Jira, and I don’t remember who made the patch for
me or if he filed a Jira on my behalf.
I vaguely recall seeing the fix in the Cassandra change logs, but I just went
and read them and I
Did the original patch make it into upstream? That's unclear. If so, what
was the JIRA #? Have you filed a JIRA for the new problem?
On Mon, Apr 13, 2015 at 12:21 PM, Robert Wille wrote:
> Back in 2.0.4 or 2.0.5 I ran into a problem with delete-only workloads. If
> I did lots of deletes and no u
Back in 2.0.4 or 2.0.5 I ran into a problem with delete-only workloads. If I
did lots of deletes and no upserts, Cassandra would report that the memtable
was 0 bytes because an accounting error. The memtable would never flush and
Cassandra would eventually die. Someone was kind enough to create
