Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 17 Jul 2014 07:29:04 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12725955.1404803533045.60577.1405582144973@arcas>
In-Reply-To: <JIRA.12725955.1404803533045@arcas>
References: <JIRA.12725955.1404803533045@arcas>
Subject: [jira] [Updated] (CASSANDRA-7511) Commit log grows infinitely after
 truncate
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict updated CASSANDRA-7511:
--------------------------------

    Labels: commitlog  (was: )

> 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
>
> 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)