hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15075) Allow region split request to carry identification information
Date Tue, 12 Jan 2016 17:27:40 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094343#comment-15094343
] 

Ted Yu commented on HBASE-15075:
--------------------------------

I compiled with:
{code}
$ java -version
java version "1.8.0_65"
Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.65-b01, mixed mode)
{code}
the compilation passed with patch v2:
{code}
[INFO] Apache HBase - External Block Cache ................ SUCCESS [  2.148 s]
[INFO] Apache HBase - Assembly ............................ SUCCESS [  9.896 s]
[INFO] Apache HBase - Shaded .............................. SUCCESS [  0.063 s]
[INFO] Apache HBase - Shaded - Client ..................... SUCCESS [  1.012 s]
[INFO] Apache HBase - Shaded - Server ..................... SUCCESS [  2.087 s]
[INFO] Apache HBase - Spark ............................... SUCCESS [ 29.575 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:11 min
[INFO] Finished at: 2016-01-12T09:26:11-08:00
{code}

> Allow region split request to carry identification information
> --------------------------------------------------------------
>
>                 Key: HBASE-15075
>                 URL: https://issues.apache.org/jira/browse/HBASE-15075
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 15075-v0.txt, 15075-v1.txt, 15075-v2.txt, HBASE-15075.v2.patch,
HBASE-15075.v3.patch
>
>
> During the process of improving region normalization feature, I found that 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.
> The association of particular split request with outcome of split would give RegionNormalizer
information so that it can make better normalization decisions in the subsequent invocations.
> One approach is to embed metadata, such as a UUID, 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).
> See discussion on dev mailing list
> http://search-hadoop.com/m/YGbbCXdkivihp2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message