Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 00B429873 for ; Tue, 12 Mar 2013 17:47:21 +0000 (UTC) Received: (qmail 2825 invoked by uid 500); 12 Mar 2013 17:47:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 2793 invoked by uid 500); 12 Mar 2013 17:47:18 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 2785 invoked by uid 99); 12 Mar 2013 17:47:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 17:47:18 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kumaramit.extra@gmail.com designates 74.125.82.178 as permitted sender) Received: from [74.125.82.178] (HELO mail-we0-f178.google.com) (74.125.82.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 17:47:13 +0000 Received: by mail-we0-f178.google.com with SMTP id o45so111286wer.37 for ; Tue, 12 Mar 2013 10:46:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=PCILXozZ9SZiuxRv4B5+0Nh2f7capDKyuWi3Ut9fqyk=; b=ruPTsVvaL0KpRrQutszykmCvZzqcDWN6gr/EnjbO0laihg84AxaQdICQqgPlbek7rr MlwU6eEBBp00V6waIGJ2QAQ545cVu3XAS6UmdbpsW2VZYkTcakjbw2YB6HF7tM+ghN62 3Bx+GFG2EC+G/gsKOUS0sNebszJ6G+K7yNiN7gkLwrxT9JXm3jAvw2HA1HMWUbFdUv86 FRDqMa7z47rlAiRAGuQxVbyLpY0uJLzvbos1bnr2fJfuPSqjqNteB6vzzGvUax7JmkDG YEv4UJliJ+pHQusBBU+xQ2VYy450M3GaEMyrgtMy0Kwl18UwA2mjwn3cLN9EA+JqjGv3 iVYQ== MIME-Version: 1.0 X-Received: by 10.194.95.198 with SMTP id dm6mr28829556wjb.6.1363110411994; Tue, 12 Mar 2013 10:46:51 -0700 (PDT) Received: by 10.180.88.34 with HTTP; Tue, 12 Mar 2013 10:46:51 -0700 (PDT) Date: Tue, 12 Mar 2013 11:46:51 -0600 Message-ID: Subject: commitlog -deleted keyspaces. From: a k To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7bb03a50e58f4604d7bddfa9 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bb03a50e58f4604d7bddfa9 Content-Type: text/plain; charset=ISO-8859-1 We are running a 4 node cluster version 1.1.0 and our commit logs seem to be ever growing. We have a total about 250 GB per node in the keyspaces/column families and the commit logs are at about 30 GB.There have been several deletions of keyspaces in our setup and I am concerned about a few things. First being the size of the commit logs, we have not modified the "commitlog_total_space_in_mb" in yaml so I assume it is the default 4092MB, We don't have "memtable_flush_after_mins" setting either. Is this sane? Why would the size of the commit logs be so large (I am worried about the startup time, when it has to replay the commit logs) and why would the default size of 4092 MB not be enforced. Would it cause us trouble when we upgrade to 1.2? Another thing I have noticed is that upon restarts, the old keyspaces that were deleted re-appear although with less data, I would imagine that has nothing to do with the commit logs. Can I safely delete the commitlogs after the nodetool flush? Many thanks Amit --047d7bb03a50e58f4604d7bddfa9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable We are running a 4 node cluster version 1.1.0 and our commit logs seem to b= e ever growing. We have a total about 250 GB per node in the keyspaces/colu= mn families and the commit logs are at about 30 GB.There have been several = deletions of keyspaces in our setup and I am concerned about a few things.<= br>
First being the size of the commit logs, we have not modified the=A0 &q= uot;commitlog_total_space_in_mb" in yaml so I assume it is the default= =A0=A0 4092MB, We don't have "memtable_flush_after_mins" sett= ing either.

Is this sane? Why would the size of the commit logs be so large (I am w= orried about the startup time, when it has to replay the commit logs) and w= hy would the default size of 4092 MB not be enforced.

Would it cause= us trouble when we upgrade to 1.2?

Another thing I have noticed is that upon restarts, the old keyspaces t= hat were deleted re-appear although with less data, I would imagine that ha= s nothing to do with the commit logs.

Can I safely delete the commit= logs after the nodetool flush?



Many thanks
Amit

--047d7bb03a50e58f4604d7bddfa9--