[
https://issues.apache.org/jira/browse/HBASE-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093664#comment-15093664
]
Ted Yu commented on HBASE-15075:
--------------------------------
>From
>https://builds.apache.org/job/PreCommit-HBASE-Build/69/artifact/patchprocess/patch-unit-hbase-server-jdk1.8.0_66.txt
{code}
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR]
/testptch/hbase/hbase-server/src/main/java/org/apache/hadoop/hbase/master/normalizer/SplitNormalizationPlan.java:[95,12]
no suitable method found for splitRegion(byte[],byte[],java.util.UUID)
method org.apache.hadoop.hbase.client.Admin.splitRegion(byte[]) is not
applicable
(actual and formal argument lists differ in length)
method org.apache.hadoop.hbase.client.Admin.splitRegion(byte[],byte[]) is
not applicable
(actual and formal argument lists differ in length)
{code}
Looks like the following addition to Admin.java was not effective:
{code}
+ void splitRegion(final byte[] regionName, final byte[] splitPoint, final
UUID id)
{code}
I built / ran test suite locally using 1.7.0_60 but didn't reproduce the above.
[~busbey]:
Do you have some idea ?
> 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)
