hbase-issues mailing list archives

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

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

Jerry He commented on HBASE-15075:
----------------------------------

Hi, [~tedyu]

A couple of comments.
Can the UUID be generated on the server?  In the Proc v2 implementation, the proc-id is generated
on the server side.
I guess using a UUID is ok in this JIRA. The proc-id in Proc v2 is a 'long'.  If it will eventually
be implemented with Proc v2, it will just be an implementation detail.
Also in this JIRA the client does not really need or need to know the UUID, since it is not
doing any tracking or waiting.

I see the RegionStateTransitionContext is getting the UUID.  But who is using this info is
not in the patch, right?
For example, the RegionStateListener you mentioned in the description.

 

> 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.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