Benedict commented on CASSANDRA-7511:

Looking at 2.1, it is actually still affected by this bug. I don't mind which 
solution we go for in 2.1; always flush, or grab the last replay position from 
the memtable (either are pretty trivial)

> Always flush on TRUNCATE
> ------------------------
>                 Key: CASSANDRA-7511
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7511
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: CentOS 6.5, Oracle Java 7u60, C* 2.0.6, 2.0.9, including 
> earlier 1.0.* versions.
>            Reporter: Viktor Jevdokimov
>            Assignee: Jeremiah Jordan
>            Priority: Minor
>              Labels: commitlog
>             Fix For: 2.0.10
>         Attachments: 7511-2.0-v2.txt, 7511-v3-remove-renewMemtable.txt, 
> 7511-v3-test.txt, 7511-v3.txt, 7511.txt
> Commit log grows infinitely after CF truncate operation via cassandra-cli, 
> regardless CF receives writes or not thereafter.
> CF's could be non-CQL Standard and Super column type. Creation of snapshots 
> after truncate is turned off.
> Commit log may start grow promptly, may start grow later, on a few only or on 
> all nodes at once.
> Nothing special in the system log. No idea how to reproduce.
> After rolling restart commit logs are cleared and back to normal. Just 
> annoying to do rolling restart after each truncate.

This message was sent by Atlassian JIRA

Reply via email to