[CASSANDRA-7511] Always flush on TRUNCATE

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 2.0.10, 2.1 rc5
• Labels: commitlog

Environment

CentOS 6.5, Oracle Java 7u60, C* 2.0.6, 2.0.9, including earlier 1.0.* versions.

• Severity: Low
• Since Version: 2.0.6
• Assignee: Jeremiah Jordan
• Reporter: Viktor Jevdokimov

Authors

Jeremiah Jordan

Reviewers

T Jake Luciani

• Tester: Ryan McGuire
• Created: 08/Jul/14 07:12
• Updated: 16/Apr/19 09:31
• Resolved: 01/Aug/14 15:21

Description

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.

Issue Links

• is duplicated by: CASSANDRA-7640 Seeing commit log grow unbounded
• is related to: CASSANDRA-7646 DROP may not clean commit log segments when auto snapshot is false
• is related to: CASSANDRA-7750 Do not flush on truncate if "durable_writes" is false.
• relates to: CASSANDRA-5704 add cassandra.unsafesystem property (Truncate flushes to disk again in 1.2, even with durable_writes=false)
• relates to: CASSANDRA-4153 Optimize truncate when snapshots are disabled or keyspace not durable