[
https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14079357#comment-14079357
]
Jeremiah Jordan commented on CASSANDRA-7511:
--------------------------------------------
Why don't we just remove the "if" here and always flush before truncate? The
flush isn't what causes the snapshot, so we aren't violating that if we flush
either way.
{noformat}
if (DatabaseDescriptor.isAutoSnapshot())
{
// flush the CF being truncated before forcing the new segment
forceBlockingFlush();
// sleep a little to make sure that our truncatedAt comes after any
sstable
// that was part of the flushed we forced; otherwise on a tie, it
won't get deleted.
Uninterruptibles.sleepUninterruptibly(1, TimeUnit.MILLISECONDS);
}
{noformat}
> 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
> Assignee: Benedict
> Priority: Minor
> Labels: commitlog
> Fix For: 2.0.10
>
> Attachments: 7511-2.0-v2.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
(v6.2#6252)
