cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Spriegel (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7511) Always flush on TRUNCATE
Date Fri, 08 Aug 2014 12:00:19 GMT


Christian Spriegel commented on CASSANDRA-7511:

The renewTable-logic was added to allow fast-truncates for automated testing (for application

Originally this was added for 1.1: CASSANDRA-4153
And with 1.2 there was another tweak on this topic: CASSANDRA-5704

Please reconsider this patch, as it will slow down truncates and will probably make automated
testing impossible again (as truncate becomes so slow it will be unusable)

> Always flush on TRUNCATE
> ------------------------
>                 Key: CASSANDRA-7511
>                 URL:
>             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: Jeremiah Jordan
>            Priority: Minor
>              Labels: commitlog
>             Fix For: 2.0.10, 2.1 rc5
>         Attachments: 7511-2.0-v2.txt, 7511-v3-remove-renewMemtable.txt, 7511-v3-test.txt,
7511-v3.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

View raw message