[
https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedict updated CASSANDRA-7511:
--------------------------------
Attachment: 7511.txt
I think this is fixed in 2.1 already, and am attaching a fix for 2.0
It should be pretty easy to replicate this issue, actually - if you truncate a
table with any data present in the memtable, the CL segment will retain dirty
values for the records in the memtable. So, insert a few records, truncate, and
then insert lots of data, enough to fill up the CL, and watch as it grows
beyond the configured limit. Might be worth creating a dtest (don't actually
need to monitor it going above the limit - if it goes above two segments is
enough).
> 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: Ryan McGuire
> Priority: Minor
> Labels: commitlog
> Attachments: 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)
