From cassandra-user-return-690-apmail-incubator-cassandra-user-archive=incubator.apache.org@incubator.apache.org Sat Sep 26 18:51:16 2009 Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 50449 invoked from network); 26 Sep 2009 18:51:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Sep 2009 18:51:14 -0000 Received: (qmail 67236 invoked by uid 500); 26 Sep 2009 18:51:14 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 66929 invoked by uid 500); 26 Sep 2009 18:51:13 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 66798 invoked by uid 99); 26 Sep 2009 18:51:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Sep 2009 18:51:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 209.85.219.205 as permitted sender) Received: from [209.85.219.205] (HELO mail-ew0-f205.google.com) (209.85.219.205) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Sep 2009 18:51:02 +0000 Received: by ewy1 with SMTP id 1so132087ewy.27 for ; Sat, 26 Sep 2009 11:50:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=LThCbMz86D6+lVKaMe4IJ3Jhzxf9phCW4vj3CKd5GsQ=; b=xiRsmEDr3jBWrbVPE8xRHMK3WewkWa0j8yB4qD+T7DnfK8feqxmlRT2OmfTqZefu93 ymvaS9pw5GZHJcn5p8HNxRut2rRrVmUTfsCwpeMB4+UHL2BCNeB52tSfXl7sXKqJMST5 tS7cXnWY40KpLySPqEwVVeTaoZhPaFEJ+5neA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=XDzepLYQtne1rjRo/Kmb5+zpqFmEr53yu7H2QCYfdpkBDysvtx61wNHqFZ99vj1dVq 2PFw0UlCoqv9xGORd/Mk2VpOg1sjgoubS/t1icHA4P9FlohJGCW+hiaC2+n/4T5gHBGD cN27a1sPqE/SobQkLIp8kdxFHI941uQC/wQdg= MIME-Version: 1.0 Received: by 10.216.49.66 with SMTP id w44mr323712web.184.1253991041626; Sat, 26 Sep 2009 11:50:41 -0700 (PDT) In-Reply-To: <23b1e84e0909252155r2fadc0b0iee76d17e66375cea@mail.gmail.com> References: <23b1e84e0909241228x7b153481k7f0e135f4d1d3fc@mail.gmail.com> <23b1e84e0909242007s7facb02evbbe60f80976dc59d@mail.gmail.com> <23b1e84e0909251133if47ba36la41545444e096b22@mail.gmail.com> <23b1e84e0909252155r2fadc0b0iee76d17e66375cea@mail.gmail.com> Date: Sat, 26 Sep 2009 13:50:41 -0500 Message-ID: Subject: Re: commit logs are not deleted From: Jonathan Ellis To: cassandra-user@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Patch 0001 on https://issues.apache.org/jira/browse/CASSANDRA-459 fixes another bug that could cause this. On Fri, Sep 25, 2009 at 11:55 PM, Igor Katkov wrote: > I checked out and built 0.4 branch. It's all the same, files stays. > I also noticed a side effect - as number of commit log segments is > growing, server response time is also growing. > I assume this is because Cassandra now has to read through some these > files on reach read/write request > > > On Fri, Sep 25, 2009 at 4:53 PM, Jonathan Ellis wrote= : >> This is fixed on the 0.4 branch (but not in trunk, yet) >> >> On Fri, Sep 25, 2009 at 1:57 PM, Jonathan Ellis wrot= e: >>> https://issues.apache.org/jira/browse/CASSANDRA-455 will address >>> FlushPeriod not working. >>> >>> On Fri, Sep 25, 2009 at 1:33 PM, Igor Katkov wrote: >>>> I tried latest stable version 0.3 and commit logs segments are in fact= deleted. >>>> Tried it again on 0.4 set =A0periodic flush to 1min >>>> (FlushPeriodInMinutes=3D"1") =3D> it's all the same, files remains the= re >>>> forever. >>>> >>>> I also noticed that there are other implicit CFs, can these prevent >>>> logs from being deleted? >>>> DEBUG - adding Channels as 0 >>>> DEBUG - adding LocationInfo as 1 >>>> DEBUG - adding HintsColumnFamily as 2 >>>> >>>> On Thu, Sep 24, 2009 at 11:07 PM, Igor Katkov wrot= e: >>>>> in my case commit log segments are never deleted (unless I restart th= e server) >>>>> so they grow and grow and eventually hosts is running out of space. >>>>> >>>>> Any ideas how to fix it? >>>>> >>>>> On Thu, Sep 24, 2009 at 8:22 PM, Jonathan Ellis w= rote: >>>>>> When all the data from a given commit log segment has been flushed a= s >>>>>> sstables, that segment can be deleted. =A0So if you do a bunch of >>>>>> inserts and then stop, it's normal to have some commitlogs around >>>>>> indefinitely. =A0All CFs are flushed on server restart, and the log >>>>>> segments can then be removed, or you can add a periodic flush to the >>>>>> CF definition so it will flush even when there has not been any extr= a >>>>>> activity. >>>>>> >>>>>> (This last part doesn't quite work as designed right now, but we're >>>>>> working on a fix: https://issues.apache.org/jira/browse/CASSANDRA-45= 5) >>>>>> >>>>>> -Jonathan >>>>>> >>>>>> On Thu, Sep 24, 2009 at 2:28 PM, Igor Katkov wro= te: >>>>>>> Hi, >>>>>>> >>>>>>> I'm using Cassandra 0.4.0 rc2 >>>>>>> >>>>>>> I can't make Cassandra to wipe commit logs. They just keep >>>>>>> accumulating, no mater what settings I play with in the config file= . >>>>>>> >>>>>>> I insert 200ooo keys. 1 CF, one column, value is 170kb, single Cass= andra node. >>>>>>> MemtableSizeInMB =3D32 >>>>>>> MemtableObjectCountInMillions =3D 0.1 >>>>>>> >>>>>>> What do I do wrong? >>>>>>> >>>>>>> Please correct me if I misunderstood how things work: >>>>>>> >>>>>>> as soon as I insert a key-column-value, it gets written to memory, = as >>>>>>> soon as [data size or # of object] (see the settings above) are >>>>>>> reached mem gets flushed to a commit log file. The very fact that I >>>>>>> have growing number of commit logs files tells me that this flushin= g >>>>>>> does happen. >>>>>>> >>>>>>> Now, commit logs records has to be transferred to the data and inde= x >>>>>>> files, I'm sure it happens as well, since my data folder is also >>>>>>> growing, I see a lot of *.db files there. >>>>>>> According to >>>>>>> http://perspectives.mvdirona.com/2009/02/07/FacebookCassandraArchit= ectureAndDesign.aspx >>>>>>> commit logs has to be wiped as soon as =A0all its column families p= ushed to disk. >>>>>>> This thing does NOT happen somehow, I have only one column family >>>>>>> defined in the conf file. >>>>>>> >>>>>>> Conf file - http://www.katkovonline.com/storage-conf.xml >>>>>>> >>>>>> >>>>> >>>> >>> >> >