[jira] [Commented] (CASSANDRA-7511) Commit log grows infinitely after truncate

["Michael Shuler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056281#comment-14056281 ] 

Michael Shuler commented on CASSANDRA-7511:
-------------------------------------------

[~vjevdokimov] without clear steps to reproduce your problem, it will be difficult to make headway towards identifying a bug.

[~enigmacurry] with the general idea pretty clear, perhaps we can try to reproduce on latest 2.0 release during a long run?

> Commit log grows infinitely after 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
>            Priority: Minor
>
> 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
(v6.2#6252)