[
https://issues.apache.org/jira/browse/HBASE-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103544#comment-15103544
]
stack commented on HBASE-15075:
-------------------------------
Lets hold on this development. It is predicated on 'During the process of
improving region normalization feature...'. My reading of the work 'improving'
region normalization is that normalization is being mangled, not improved....
That would undo the predicate for this work.
> 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
> Fix For: 2.0.0, 1.3.0
>
> Attachments: 15075-v0.txt, 15075-v1.txt, 15075-v2.txt,
> HBASE-15075.v10.patch, HBASE-15075.v2.patch, HBASE-15075.v3.patch,
> HBASE-15075.v4.patch, HBASE-15075.v5.patch, HBASE-15075.v6.patch,
> HBASE-15075.v7.patch, HBASE-15075.v8.patch, HBASE-15075.v9.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)
