You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/01/12 03:04:39 UTC
[jira] [Updated] (HBASE-15075) Allow region split request to carry
identification information
[ https://issues.apache.org/jira/browse/HBASE-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-15075:
---------------------------
Summary: Allow region split request to carry identification information (was: Allow region split request to carry metadata)
> 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)