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

Mikhail Antonov commented on HBASE-15075:
-----------------------------------------

I'd say if we need to have structure to keep track of failed plans, we may not 
need to have recent plans? I think logic inside region normalizer or master to 
actually use failedPlans data structure could be implemented in another jira, 
but it may be good to have this structure itself populated in this one, so we 
better who who and how keeps and updates failed plans, what do you think?

API-wise,  setRegionStateListener should be renamed to add* now? Why do we need 
this as part of this patch btw?

> 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.v2.patch, HBASE-15075.v3.patch, HBASE-15075.v4.patch, 
> HBASE-15075.v5.patch, HBASE-15075.v6.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)

Reply via email to