Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8F0751149C for ; Thu, 4 Sep 2014 04:37:38 +0000 (UTC) Received: (qmail 50411 invoked by uid 500); 4 Sep 2014 04:37:38 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 50321 invoked by uid 500); 4 Sep 2014 04:37:38 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 50310 invoked by uid 99); 4 Sep 2014 04:37:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Sep 2014 04:37:37 +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: domain of ashish.singhi@huawei.com designates 119.145.14.64 as permitted sender) Received: from [119.145.14.64] (HELO szxga01-in.huawei.com) (119.145.14.64) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Sep 2014 04:37:32 +0000 Received: from 172.24.2.119 (EHLO szxeml403-hub.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CBF34224; Thu, 04 Sep 2014 12:37:09 +0800 (CST) Received: from SZXEML513-MBS.china.huawei.com ([169.254.8.232]) by szxeml403-hub.china.huawei.com ([::1]) with mapi id 14.03.0158.001; Thu, 4 Sep 2014 12:37:02 +0800 From: ashish singhi To: "dev@hbase.apache.org" Subject: Writer for a hfile is rolled though it has not reached max size Thread-Topic: Writer for a hfile is rolled though it has not reached max size Thread-Index: AQHPx/nezLetjKIkCU62Jv7+Rnj7JQ== Date: Thu, 4 Sep 2014 04:37:01 +0000 Message-ID: <8E858C3A39F0D046B420FBA6F75448C02FABB56B@szxeml513-mbs.china.huawei.com> Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.18.168.119] Content-Type: multipart/alternative; boundary="_000_8E858C3A39F0D046B420FBA6F75448C02FABB56Bszxeml513mbschi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Virus-Checked: Checked by ClamAV on apache.org --_000_8E858C3A39F0D046B420FBA6F75448C02FABB56Bszxeml513mbschi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all. When a writer for a column family exceeds the hregion.max.filesize then we= are rolling writers of all the column families though the writers of the o= ther column family has not exceeded the max size. Below is the code snippet from HFileOutputFormat2 class. {code} // If any of the HFiles for the column families has reached // maxsize, we need to roll all the writers if (wl !=3D null && wl.written + length >=3D maxsize) { this.rollRequested =3D true; } // This can only happen once a row is finished though if (rollRequested && Bytes.compareTo(this.previousRow, rowKey) !=3D= 0) { rollWriters(); } {code} Is it a bug or I am missing something ? Regards, Ashish Singhi --_000_8E858C3A39F0D046B420FBA6F75448C02FABB56Bszxeml513mbschi_--