Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of shahab.yunus@gmail.com
 designates 209.85.215.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEo-6+SM4qZK6Gm=JtcnaUCa4Tw=XXQcRRaMfpsAC9sS8-xU4A@mail.gmail.com>
References: 
 <CAEo-6+SM4qZK6Gm=JtcnaUCa4Tw=XXQcRRaMfpsAC9sS8-xU4A@mail.gmail.com>
Date: Fri, 14 Nov 2014 10:04:14 -0500
Message-ID: 
 <CAEo-6+TDiSpLVyKxJAA4VdzSBBy--4YcsgfHH3GCT11SCh9q3w@mail.gmail.com>
Subject: Re: Forcibly merging regions
From: Shahab Yunus <shahab.yunus@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11c3ee743211460507d2f166

--001a11c3ee743211460507d2f166
Content-Type: text/plain; charset=UTF-8

Related to this...can hbase.hregion.max.filesize setting prevent merging of
table regions? Or regions are merged anyway but they get split again during
compaction?

Regards,
Shahab

On Fri, Nov 14, 2014 at 9:41 AM, Shahab Yunus <shahab.yunus@gmail.com>
wrote:

> The documentation of online merge tool (merge_region) states that if we
> forcibly merge regions (by setting the 3rd attribute as true) then it can
> create overlapping regions. if this happens then will this render the
> region or table unusable or it is just a performance hit? I mean how bigger
> of a deal it is?
>
> Actually, we are merging regions using the programmatic API for this and
> setting this flag ('forcible') as false. But for some tables (we haven't
> figured out a pattern yet, data is still accessible), merge of regions do
> not happen at all. Afterwards we tried with this flag = true, and it still
> doesn't merge them.
>
> CDH 5.1.0
> (Hbase is 0.98.1-cdh5.1.0)
>
> Regards,
> Shahab
>

--001a11c3ee743211460507d2f166--