Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CALte62yaqW3g_S_U8bDMO9=N0H-7+-Yib7s+FswidRE_qE3uqw@mail.gmail.com>
References: 
 <CALte62yaqW3g_S_U8bDMO9=N0H-7+-Yib7s+FswidRE_qE3uqw@mail.gmail.com>
From: Mikhail Antonov <olorinbant@gmail.com>
Date: Wed, 6 Jan 2016 10:14:19 -0800
Message-ID: 
 <CAHxLZBVAbHqd8Rb14rfrhChHYno6oq-Yu3r2Fa-fYuVCKN4AeQ@mail.gmail.com>
Subject: Re: identifying source of region split request
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11c301cc6b43c70528ae5440

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

Adding this tracing information to know who initiated split is in general
useful thing. Right now though I'm not sure I see how that would help to
make better normalization decisions? Region split failure implies
underlying FS issue? Any examples/ideas?

Kind of..collect statistics to blacklist some RSs with high failure rate
and don't attempt to split regions hosted there in future?

On Tue, Jan 5, 2016 at 2:55 PM, Ted Yu <yuzhihong@gmail.com> wrote:

> Hi,
> I recently worked on improving region normalization feature.
>
> If region split request triggered by the execution of
> SplitNormalizationPlan fails, there is no way of knowing whether the failed
> split originated from region normalization.
> Such association would give RegionNormalizer information so that it can
> make better normalization decisions in the subsequent invocations.
>
> One enhancement I can think of is to embed metadata in SplitRequest which
> gets passed through RegionStateTransitionContext when
> RegionServerServices#reportRegionStateTransition() is called.
> This way, RegionStateListener can be notified with the metadata (id of the
> requester).
>
> Comment is welcome.
>


-- 
Thanks,
Michael Antonov

--001a11c301cc6b43c70528ae5440--