From user-return-51276-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org Tue May 3 01:42:03 2016 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 4A12718257 for ; Tue, 3 May 2016 01:42:03 +0000 (UTC) Received: (qmail 47780 invoked by uid 500); 3 May 2016 01:42:01 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 47706 invoked by uid 500); 3 May 2016 01:42:01 -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 47694 invoked by uid 99); 3 May 2016 01:42:00 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2016 01:42:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3841C18053D for ; Tue, 3 May 2016 01:42:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id UQEOu6UK7_Zi for ; Tue, 3 May 2016 01:41:59 +0000 (UTC) Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 1BCC15F60E for ; Tue, 3 May 2016 01:41:59 +0000 (UTC) Received: by mail-wm0-f48.google.com with SMTP id e201so127335492wme.0 for ; Mon, 02 May 2016 18:41:59 -0700 (PDT) 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; bh=uTJ+EBp2iJGuOykGJv6CJySwSJguMebiDWtLx3o+Pvw=; b=r3fJMGrGj1KtDkAKsQtN2vcpAgi5ewRSppzh6EQSjaRv9FpEhtX5dmwXoS00uELcM2 z3hmJo3EcE2MEJQQxXsZOc7tSsSHYDw3TRwUfYPt7aqgqHyTy1eyxa0PKhCLfPhx0XFk oQggRzLf57UuvNI5HFsfdJV0ERJ4Gl/xN3RaJ/RTfY9TatTuTOYd+xj138DEZiYs17af bboX7wPC0nR9jaG7ghiO6LZQowboyur4Y9EBHIMPiQoFv0zMTXF8NBdgkMuwDrmDY2BB Ohl38bJAjDfcEHOTeJnYpjobjoVh04YNgsRkkI4OqipKucyWhzVqt3uo9YGlAu0pMKlk 9BbA== 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:date :message-id:subject:from:to; bh=uTJ+EBp2iJGuOykGJv6CJySwSJguMebiDWtLx3o+Pvw=; b=VypV0aV8mDldHFOvNWIrcNZLnXluEAE05fT8ieK3Om0nE6vU98NFh9pbYaPxECFQkE GUCe0xtMoLnKIgSu4FSSx8xy2Cut5Enoil6cyDIYVPcP/NuFH9eR8u/smM/aPRl7xyCM aZZs0hSVDp3gpsLxcG/wX9z+v56ndkjDbrKVlaum3g2bcRYOwEvfHNrkhsi1v/cRrOdu CnMlYnVqD6j2dRnLeO07NGgSR6a/9JUJRLSmumcKtLP7nWxpMpSuP2J9Icna80cv2D/5 peuDtNs0RAMfALt8EYmhZQPgB7YGshWP2f+0vGxaTSi50EnMnSuDL9BHDlA/eRs1BoEO 0jjw== X-Gm-Message-State: AOPr4FXFL2MbD0q/dhYx2OW81Tvf1vmzEJsZf8CrS0RlSBLzFRVGgoiYSsgoRLa3Q4Fl1lJBiNtP/HomLIZHhA== MIME-Version: 1.0 X-Received: by 10.195.20.66 with SMTP id ha2mr38455988wjd.76.1462239717516; Mon, 02 May 2016 18:41:57 -0700 (PDT) Received: by 10.194.113.35 with HTTP; Mon, 2 May 2016 18:41:57 -0700 (PDT) In-Reply-To: References: Date: Tue, 3 May 2016 09:41:57 +0800 Message-ID: Subject: Re: How can i get hbase table memory used? Why hdfs size of hbase table double when i use bulkload? From: Jone Zhang To: user Content-Type: multipart/alternative; boundary=001a11367dd2f06eb40531e6361e --001a11367dd2f06eb40531e6361e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable For #1 My workload is read heavy. I use bulkload to write data once a day. Thanks. 2016-04-30 1:13 GMT+08:00 Ted Yu : > For #1, can you clarify whether your workload is read heavy, write heavy = or > mixed load of read and write ? > > For #2, have you run major compaction after the second bulk load ? > > On Thu, Apr 28, 2016 at 9:16 PM, Jone Zhang > wrote: > > > *1=E3=80=81How can i get hbase table memory used?* > > *2=E3=80=81Why hdfs size of hbase table double when i use bulkload* > > > > bulkload file to qimei_info > > > > 101.7 G /user/hbase/data/default/qimei_info > > > > bulkload same file to qimei_info agagin > > > > 203.3 G /user/hbase/data/default/qimei_info > > > > hbase(main):001:0> describe 'qimei_info' > > DESCRIPTION > > > > > > 'qimei_info', {NAME =3D> 'f', DATA_BLOCK_ENCODING =3D> 'NONE', BLOOMFI= LTER > =3D> > > 'ROW', REPLICATION_SCOPE =3D> '0', VERSIONS =3D> ' > > > > 1', COMPRESSION =3D> 'LZO', MIN_VERSIONS =3D> '0', TTL =3D> '214748364= 7', > > KEEP_DELETED_CELLS =3D> 'false', BLOCKSIZE =3D> '65536', > > > > IN_MEMORY =3D> 'false', BLOCKCACHE =3D> 'true'} > > > > > > 1 row(s) in 1.4170 seconds > > > > > > *Besh wishes.* > > *Thanks.* > > > --001a11367dd2f06eb40531e6361e--