[jira] [Comment Edited] (CASSANDRA-7511) Always flush on TRUNCATE

["Christian Spriegel (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090675#comment-14090675 ] 

Christian Spriegel edited comment on CASSANDRA-7511 at 8/8/14 12:02 PM:
------------------------------------------------------------------------

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

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)


Edit: could the patch being changed so that renew is only used only when durable_writes if off? Shouldnt that solve the growing commitlog issue?


was (Author: christianmovi):
The renewTable-logic was added to allow fast-truncates for automated testing (for application developers).

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: 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: 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
(v6.2#6252)