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 A7B95DB17 for ; Thu, 8 Nov 2012 08:09:22 +0000 (UTC) Received: (qmail 65682 invoked by uid 500); 8 Nov 2012 08:09:20 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 65563 invoked by uid 500); 8 Nov 2012 08:09:19 -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 65519 invoked by uid 99); 8 Nov 2012 08:09:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 08:09:18 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pengyunmomo@gmail.com designates 209.85.160.169 as permitted sender) Received: from [209.85.160.169] (HELO mail-gh0-f169.google.com) (209.85.160.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 08:09:08 +0000 Received: by mail-gh0-f169.google.com with SMTP id r1so557893ghr.14 for ; Thu, 08 Nov 2012 00:08:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=5e62BrsdnvZMGLA8NQrwi5LLPWC7sZkHKgsBGx1grQ8=; b=iXBhSb2dy3kyRbZiJiHEB28ZYAlvJ5vK4e/7XEigcEp7dsKRaQeuGZNIQiLtBi6aD7 b+gywWZK57c15zFxLvqW8CE503oQddvaycMLyLN/ClPvm6ZwFtjd4FnbntIHeCsh/pX8 czZ4gEEEhxBK/NHUWFucknFoSp2xC2i4QvM0IOeGcU8Bwih/cSCOl2ULx018OFzNgyba ZmN20IfCminitHmFwQ7DMNoIUhvbLQHMQ6yN1EGP4f9VRtp8ECKeoKJnuOdgZELQnnXg MU2ZGpgUQxh1C0KSrqJbs9gDIrnwSZZFNdLiJWVDeBkmH9D9e532UJlDUreyl/m+FtfI Xpig== Received: by 10.236.142.139 with SMTP id i11mr7517012yhj.24.1352362128022; Thu, 08 Nov 2012 00:08:48 -0800 (PST) Received: from [10.0.0.4] (c-76-17-119-179.hsd1.ga.comcast.net. [76.17.119.179]) by mx.google.com with ESMTPS id o66sm26226177yhi.19.2012.11.08.00.08.47 (version=SSLv3 cipher=OTHER); Thu, 08 Nov 2012 00:08:47 -0800 (PST) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Cc: "user@hbase.apache.org" X-Mailer: iPad Mail (10A523) From: PG Subject: Re: How to check if a major_compact is done? Date: Thu, 8 Nov 2012 03:08:46 -0500 To: "user@hbase.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org Hi, thanks for the comments. One thing is,,,, shouldn't web UI comes from th= e hbase API, or can I issue function call to get the progress of compaction?= . Hun On Nov 8, 2012, at 1:33 AM, ramkrishna vasudevan wrote: > There is no interface which says that the major compaction is completed. > But you can see that major compaction is in progress from the web UI. > Sorry if am wrong here. >=20 > Regards > Ram >=20 > On Thu, Nov 8, 2012 at 11:38 AM, yun peng wrote: >=20 >> Hi, All, >> I want to measure the duration of a major compaction in HBase. Since the >> function call majorCompact is asynchronous, I may need to manually check >> when the major compaction is done. Does Hbase (as of version 0.92.4) >> provide an interface to determine completion of major compaction? Thanks.= >> Yun >>=20