[
https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedict updated CASSANDRA-7511:
--------------------------------
Attachment: 7511-2.0-v2.txt
Attaching an updated patch for 2.0
For 2.1, I would like to modify the behaviour of truncate, and have it rely
explicitly on ReplayPosition since this is considerably safer. However whilst
more correct it has its own challenges, as we do not have an easy way to find
the ReplayPosition relating to a hint/batchlog entry, but we *could* serialize
these alongside, which is the most correct thing to do.
> 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)
