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 Wed, 13 Jan 2016 23:43:39 GMT

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

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

w.r.t. hadoopcheck
https://builds.apache.org/job/PreCommit-HBASE-Build/98/artifact/patchprocess/patch-javac-2.4.0.txt
:
{code}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project hbase-assembly: Error rendering velocity resource. Error invoking method
'get(java.lang.Integer)' in java.util.ArrayList at META-INF/LICENSE.vm[line 1627, column 22]:
InvocationTargetException: Index: 0, Size: 0 -> [Help 1]
[ERROR] 
{code}
Similar error seen in https://builds.apache.org/job/PreCommit-HBASE-Build/98/artifact/patchprocess/patch-javac-2.6.1.txt

Not caused by the patch where every file touched by the patch has Apache license

> 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, HBASE-15075.v4.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