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 1F9FB6C76 for ; Thu, 21 Jul 2011 09:18:27 +0000 (UTC) Received: (qmail 3513 invoked by uid 500); 21 Jul 2011 09:18:24 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 3091 invoked by uid 500); 21 Jul 2011 09:18:08 -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 3071 invoked by uid 99); 21 Jul 2011 09:18:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2011 09:18:04 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cassandralearner@gmail.com designates 209.85.210.66 as permitted sender) Received: from [209.85.210.66] (HELO mail-pz0-f66.google.com) (209.85.210.66) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2011 09:17:57 +0000 Received: by pzk34 with SMTP id 34so302438pzk.1 for ; Thu, 21 Jul 2011 02:17:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Q/MIE4uni6cmMo1bkOKwBPH44yv24Sx9Ezh8nILU/1c=; b=JFt51bVOvS+d+tGTNrpvbr8h3kHq+Q6qmdPWvAu2bZu//EKOA4g93Ncu+2NEnbQ9Nl M51UGpxa1MFixUduybNaFeBC99QzSinmDPwgmP1RL1mnaKRvIE54halaGQoqd0Pclk2Z Y7o6WzCijnh+q6oL8FEijlOAk/J2PnkQJypMc= MIME-Version: 1.0 Received: by 10.68.51.39 with SMTP id h7mr10457633pbo.428.1311239856080; Thu, 21 Jul 2011 02:17:36 -0700 (PDT) Received: by 10.68.58.230 with HTTP; Thu, 21 Jul 2011 02:17:36 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Jul 2011 14:47:36 +0530 Message-ID: Subject: Re: Memtables stored in which location From: CASSANDRA learner To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec53963a8d6489304a890d107 --bcaec53963a8d6489304a890d107 Content-Type: text/plain; charset=ISO-8859-1 Hi, You r right but i too have some concerns... Any ways , some where memtable has to be stored right, like we say memtable data is flushed to create sstable on disk. Exactly from which location or memory it will be getting from. is it like an objects streams or like it is storing the values in commitlog. my next question is , data is written to commit log. all the data is available here, and the sstable are getting created on disk, then where and when these memtables are coming into picture On Thu, Jul 21, 2011 at 1:44 PM, samal wrote: > SSTable is stored on disk not memtable. > > Memtable is memory representation of data, which is on flush to create > SSTable on disk. > > This is the location where SSTable is stored > https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L71 > > > Where as Commitlog which is back up (log) for memtable replaying store in > https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L75 > location. > > Once the all memtable is flushed to disk, new commit log segment is > created. > > On Thu, Jul 21, 2011 at 1:12 PM, Abdul Haq Shaik < > abdulsk.cassandra@gmail.com> wrote: > >> Hi, >> >> Can you please let me know where exactly the memtables are getting stored. >> I wanted to know the physical location >> > > --bcaec53963a8d6489304a890d107 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

You r right but i too have some concerns...

Any ways , some where memtable has to be stored right, like we say memtable= data is flushed to create sstable on disk.
Exactly from which location or memory it will be getting from. is it like a= n objects streams or like it is storing the values in commitlog.
my next= question is , data is written to commit log. all the data is available her= e, and the sstable are getting created on disk, then where and when these m= emtables are coming into picture

On Thu, Jul 21, 2011 at 1:44 PM, samal <samal@wakya.in> wrote:
SSTable is stored on disk not memtable.

Memtable is memory rep= resentation of data, which is on flush to create SSTable on disk.

This is the location where SSTable is stored


Where as Commitlog which is back up (log= ) for memtable replaying store in
https://gith= ub.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L75
location.

Once the all memtable is flushed to= disk, new commit log segment is created.

<= div class=3D"gmail_quote">On Thu, Jul 21, 2011 at 1:12 PM, Abdul Haq Shaik = <abdulsk.cassandra@gmail.com> wrote:
Hi,

Can you please let me= know where exactly the memtables are getting stored. I wanted to know the = physical location


--bcaec53963a8d6489304a890d107--