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 40E7C106C3 for ; Tue, 25 Feb 2014 12:14:11 +0000 (UTC) Received: (qmail 3084 invoked by uid 500); 25 Feb 2014 12:14:04 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 2094 invoked by uid 500); 25 Feb 2014 12:14:03 -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 563 invoked by uid 99); 25 Feb 2014 12:13:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Feb 2014 12:13:59 +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: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.220.177] (HELO mail-vc0-f177.google.com) (209.85.220.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Feb 2014 12:13:55 +0000 Received: by mail-vc0-f177.google.com with SMTP id if11so6997824vcb.22 for ; Tue, 25 Feb 2014 04:13:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=WZuyTHaDGOSKXH6euf7S/1H0Ze6CSCK4/BBm23dMB3A=; b=chnc+vuWmQ2oGckLofwayXuMJo2TYioAIBpEa8AvL9jF9S6CipLnIHzgxY7te2ExDz vu3jhlCeCsH21WIa535X0ALWG/7yfMdwejLk4n0yN413BtH8/Bv9htYzpykLC4d0ie3l YRZs12cAVtPRZXWNJs/MmFRG/M4zY3wy6hL0EBiSKrMpoTdmHs1bqnXY54Pc5b9cqDIW dQt4QqhfBHY/ilwNrtMNXWWuURnVFShCLMArVVwrlV/ikgXe0L5Pepjy819N7aaWIdV1 wwsXtuQ0+LlGuMDX/gHl4QdH9VPeZT4Vk7ecZBEedCLrvEHJisuHNgH+dBZkbXgBknp6 llvA== X-Gm-Message-State: ALoCoQntOliuSOR5hJy9RhE8sn43HWznnXHcn/MWZoWHpiyxA8fr8/gP2a61mCMiPhhi5/kB0WI7 X-Received: by 10.58.188.78 with SMTP id fy14mr852210vec.23.1393330414560; Tue, 25 Feb 2014 04:13:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.227.8 with HTTP; Tue, 25 Feb 2014 04:13:14 -0800 (PST) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Tue, 25 Feb 2014 07:13:14 -0500 Message-ID: Subject: Re: Is hbase call delete request for old hfile(storeFile) file if minor/major compaction happen for them To: user Content-Type: multipart/alternative; boundary=089e013a12f06a415004f33a0417 X-Virus-Checked: Checked by ClamAV on apache.org --089e013a12f06a415004f33a0417 Content-Type: text/plain; charset=UTF-8 Hi Upendra, Olds files are moved by HBase later. Take a look at org.apache.hadoop.hbase.master.CatalogJanitor JM 2014-02-25 6:25 GMT-05:00 Upendra Yadav : > Thanks... > > > On Tue, Feb 25, 2014 at 2:18 PM, Bharath Vissapragada < > bharathv@cloudera.com > > wrote: > > > In short, it needn't "download" files, that metadata is stored and > exposed > > in the API of a StoreFile and regionserver just calls that method! > > > > > > On Tue, Feb 25, 2014 at 2:16 PM, Bharath Vissapragada < > > bharathv@cloudera.com > > > wrote: > > > > > Not sure what you are asking but if you want to know the size of a > store > > > file, you can use this method, > > > > > > > > > > > > https://github.com/apache/hbase/blob/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFile.java#L1440 > > > > > > One such usage is here, > > > > > > > > > > > > https://github.com/apache/hbase/blob/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/RatioBasedCompactionPolicy.java#L292 > > > > > > It gets the sizes of all the store files, I believe thats what you are > > > asking! Please correct me if I'm wrong, > > > > > > > > > On Tue, Feb 25, 2014 at 12:37 PM, Upendra Yadav > >wrote: > > > > > >> Is hbase call delete request for old hfile(storeFile) file if > > minor/major > > >> compaction happen for them and generate new hfile and store it in > hdfs. > > >> > > >> for minor compaction how it will get size of every hfile. lets we have > > 20 > > >> no. of hfiles for a CF and minor compaction wants to perform. Will it > > >> download all hfile and decide compaction have to do or not. Or it have > > >> in-memory hfile's size information for all hfile. > > >> > > > > > > > > > > > > -- > > > Bharath Vissapragada > > > > > > > > > > > > > > -- > > Bharath Vissapragada > > > > > --089e013a12f06a415004f33a0417--