Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 43B8310E04 for ; Sun, 10 Nov 2013 21:10:32 +0000 (UTC) Received: (qmail 72631 invoked by uid 500); 10 Nov 2013 21:10:30 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 72573 invoked by uid 500); 10 Nov 2013 21:10:30 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 72565 invoked by uid 99); 10 Nov 2013 21:10:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Nov 2013 21:10:30 +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 (nike.apache.org: domain of asaf.mesika@gmail.com designates 209.85.219.45 as permitted sender) Received: from [209.85.219.45] (HELO mail-oa0-f45.google.com) (209.85.219.45) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Nov 2013 21:10:24 +0000 Received: by mail-oa0-f45.google.com with SMTP id m1so1428390oag.4 for ; Sun, 10 Nov 2013 13:10:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=l6wpzIx0BQXO5bA4ABkG2zKGtaEfugQWURGy7JLUzKo=; b=Yd3PVojsKRyLhIyT76oDMMcRfvmIXtvLnxigR84b2atCQY7jSIA8m0WlMBrCQj3767 EiZA5dRccL83pDa858OpoXQ26OG0EM2/sA+YyvYEr9ZekGxxl3tQr3HIKHrRHleoTiLx o0drakfPgD38HaQASF3BtBAlMAZVjNaGH5eCm05zpniPU0eyctZBO/I32td7kmXTRJ/9 /iIwYUJI8btb+Txj1JHR725DAaEmFWKzg+1EH5AkfWi1F1B6ywBsARiGOmo4RZhp3WLE Q4cSVM/2tR+JUuskacbfuEAdcx3TxoZzqmvC4P7/IYyA9rPVi0lvk/+ArL95ZRkQO7za COug== MIME-Version: 1.0 X-Received: by 10.60.68.10 with SMTP id r10mr21383oet.62.1384117803392; Sun, 10 Nov 2013 13:10:03 -0800 (PST) Received: by 10.60.120.37 with HTTP; Sun, 10 Nov 2013 13:10:03 -0800 (PST) In-Reply-To: References: Date: Sun, 10 Nov 2013 23:10:03 +0200 Message-ID: Subject: Re: So where is the store file flushed to? From: Asaf Mesika To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a11331258ffa4a704ead90985 X-Virus-Checked: Checked by ClamAV on apache.org --001a11331258ffa4a704ead90985 Content-Type: text/plain; charset=UTF-8 Also note that due to HDFS placement policy the store file is written locally - we'll first replica of each of its blocks so it's dispersed amongst the drives you have onto on the data node which is also the region server. On Thursday, November 7, 2013, Ted Yu wrote: > The store file is flushed to hdfs. > > bq. final compacted files will be written to HDFS, am i right? > > True. > > > On Thu, Nov 7, 2013 at 7:27 AM, Jia Wang > > wrote: > > > Hi Folks > > > > "When something is written to HBase, it is first written to an in-memory > > store (memstore), once this memstore reaches a certain size, it is > flushed > > to disk into a store file." So where is the store file flushed to? Local > > storage of the region server? Or HDFS? > > > > I'm a bit confused in this part, as I know the final compacted files will > > be written to HDFS, am i right? > > > > Thanks > > Ramon > > > --001a11331258ffa4a704ead90985--