From cassandra-user-return-715-apmail-incubator-cassandra-user-archive=incubator.apache.org@incubator.apache.org Tue Sep 29 03:22:02 2009 Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 11527 invoked from network); 29 Sep 2009 03:22:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Sep 2009 03:22:02 -0000 Received: (qmail 78132 invoked by uid 500); 29 Sep 2009 03:22:02 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 78073 invoked by uid 500); 29 Sep 2009 03:22:02 -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 78064 invoked by uid 99); 29 Sep 2009 03:22:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2009 03:22:01 +0000 X-ASF-Spam-Status: No, hits=-1.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED X-Spam-Check-By: apache.org Received-SPF: unknown (athena.apache.org: error in processing during lookup of junrao@almaden.ibm.com) Received: from [32.97.182.142] (HELO e2.ny.us.ibm.com) (32.97.182.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2009 03:21:51 +0000 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e2.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id n8T3EcFH015338 for ; Mon, 28 Sep 2009 23:14:38 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id n8T3LT0M238170 for ; Mon, 28 Sep 2009 23:21:29 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n8T3LTcl029505 for ; Mon, 28 Sep 2009 23:21:29 -0400 Received: from d01ml604.pok.ibm.com (d01ml604.pok.ibm.com [9.56.227.90]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n8T3LTrM029498 for ; Mon, 28 Sep 2009 23:21:29 -0400 In-Reply-To: <23b1e84e0909281632h1d1b7a25r16c7e1411c58164f@mail.gmail.com> References: <23b1e84e0909241228x7b153481k7f0e135f4d1d3fc@mail.gmail.com> <23b1e84e0909262203w73060b46veb351768bd9fefe2@mail.gmail.com> <23b1e84e0909270839ra1e6f2chb151885d1aa9e866@mail.gmail.com> <23b1e84e0909270918w5e1d7af3yf63570263b40a4e5@mail.gmail.com> <23b1e84e0909270920h4a5b1fb8m2bc7d004b95ec49d@mail.gmail.com> <23b1e84e0909281240u6266d359g1966e357118aff27@mail.gmail.com> <23b1e84e0909281632h1d1b7a25r16c7e1411c58164f@mail.gmail.com> Subject: Re: commit logs are not deleted X-KeepSent: C1C42612:ABB67607-88257640:00124445; type=4; name=$KeepSent To: cassandra-user@incubator.apache.org X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009 Message-ID: From: Jun Rao Date: Mon, 28 Sep 2009 20:21:22 -0700 X-MIMETrack: Serialize by Router on D01ML604/01/M/IBM(Release 8.5|December 05, 2008) at 09/28/2009 23:21:29 MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=07BBFCD3DF81C2D58f9e8a93df938690918c07BBFCD3DF81C2D5" Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org --0__=07BBFCD3DF81C2D58f9e8a93df938690918c07BBFCD3DF81C2D5 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: quoted-printable A solution to this problem is to still call discardCompletedSegments() = when flushing an empty memtable. Jun IBM Almaden Research Center K55/B1, 650 Harry Road, San Jose, CA 95120-6099 junrao@almaden.ibm.com Igor Katkov wrote on 09/28/2009 04:32:06 PM: > [image removed] > > Re: commit logs are not deleted > > Igor Katkov > > to: > > cassandra-user > > 09/28/2009 04:33 PM > > Please respond to cassandra-user > > Excellent! Many thanks. > > It works, but there is a minor thing: > the very first created commit log segment does not get deleted. > Log if filled with lines like > Not safe to delete commit log d:/cassandra-4/data/commitlog > \CommitLog-1254177667321.log; dirty is 1, > > On Mon, Sep 28, 2009 at 5:21 PM, Jonathan Ellis wrote: > I have a fix now at > https://issues.apache.org/jira/browse/CASSANDRA-459 -- only applies t= o > current trunk. =A0When Jun finishes reviewing I will backport to 0.4.= > > Sorry for the wait, > > -Jonathan > > On Mon, Sep 28, 2009 at 2:40 PM, Igor Katkov wrot= e: > > Does anyone else has the same problem with 0.4? > > As far as I know Digg and Rackspace are biggest adopters of Cassand= ra. They > > must be running 0.3 then. > > > > > > On Sun, Sep 27, 2009 at 12:20 PM, Igor Katkov wrote: > >> > >> full log is here (new) > >> http://www.katkovonline.com/cassandra-log.zip > >> > >> On Sun, Sep 27, 2009 at 12:18 PM, Igor Katkov wrote: > >>> > >>> There is no log lines with "column family 1" > >>> There are only "column family 0" > >>> > >>> On Sun, Sep 27, 2009 at 12:02 PM, Jonathan Ellis > >>> wrote: > >>>> > >>>> we're looking for "column family 1" > >>>> > > > >= --0__=07BBFCD3DF81C2D58f9e8a93df938690918c07BBFCD3DF81C2D5 Content-type: text/html; charset=ISO-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable

A solution to this problem is to still call discardCompletedSegments() when flushing an empty memtable.
Jun
IBM Almaden Research Center
K55/B1, 650 Harry Road, San Jose, CA 95120-6099

junrao@almaden.ibm.com


Igor Katkov <ikatkov@gmail.com> wrote on 09/28/2009 04:32:06 = PM:

> [image removed]

>
> Re: commit logs are not deleted

>
> Igor Katkov

>
> to:

>
> cassandra-user

>
> 09/28/2009 04:33 PM

>
> Please respond to cassandra-user

>
> Excellent! Many thanks.
>
> It works, but there is a minor thing:
> the very first created commit log segment does not get deleted. > Log if filled with lines like
> Not safe to delete commit log d:/cassandra-4/data/commitlog
> \CommitLog-1254177667321.log; dirty is 1,
>

> On Mon, Sep 28, 2009 at 5:21 PM, Jonathan Ellis <jbellis@gm= ail.com> wrote:
> I have a fix now at
> ht= tps://issues.apache.org/jira/browse/CASSANDRA-459 -- only applies t= o
> current trunk. =A0When Jun finishes reviewing I will backport to 0= .4.
>
> Sorry for the wait,
>
> -Jonathan

>
> On Mon, Sep 28, 2009 at 2:40 PM, Igor Katkov <ikatkov@gmail.com= > wrote:
> > Does anyone else has the same problem with 0.4?
> > As far as I know Digg and Rackspace are biggest adopters of C= assandra. They
> > must be running 0.3 then.
> >
> >
> > On Sun, Sep 27, 2009 at 12:20 PM, Igor Katkov <ikatkov@gma= il.com> wrote:
> >>
> >> full log is here (new)
> >> http://www.katkovonline.com/cassandra-log.zip
> >>
> >> On Sun, Sep 27, 2009 at 12:18 PM, Igor Katkov <ikatkov= @gmail.com> wrote:
> >>>
> >>> There is no log lines with "column family 1"= ;
> >>> There are only "column family 0"
> >>>
> >>> On Sun, Sep 27, 2009 at 12:02 PM, Jonathan Ellis <= jbellis@gmail.com>
> >>> wrote:
> >>>>
> >>>> we're looking for "column family 1"
= > >>>>
> >
> >
= --0__=07BBFCD3DF81C2D58f9e8a93df938690918c07BBFCD3DF81C2D5--