Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 883B7115F9 for ; Mon, 4 Aug 2014 08:36:14 +0000 (UTC) Received: (qmail 91291 invoked by uid 500); 4 Aug 2014 08:36:14 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 91255 invoked by uid 500); 4 Aug 2014 08:36:14 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 91242 invoked by uid 99); 4 Aug 2014 08:36:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Aug 2014 08:36:14 +0000 Date: Mon, 4 Aug 2014 08:36:14 +0000 (UTC) From: "Sylvain Lebresne (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-7511) Always flush on TRUNCATE MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-7511: ---------------------------------------- Fix Version/s: (was: 2.1.0) 2.1 rc5 > 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)