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

Hudson commented on HBASE-22074:
--------------------------------

Results for branch branch-2
        [build #1776 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1776/]: 
(/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1776//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1776//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1776//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Should use procedure store to persist the state in reportRegionStateTransition
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-22074
>                 URL: https://issues.apache.org/jira/browse/HBASE-22074
>             Project: HBase
>          Issue Type: Bug
>          Components: amv2, proc-v2
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Blocker
>             Fix For: 3.0.0, 2.2.0, 2.3.0
>
>         Attachments: HBASE-22074-v1.patch, HBASE-22074-v2.patch, 
> HBASE-22074-v3.patch, HBASE-22074-v3.patch, HBASE-22074-v4.patch, 
> HBASE-22074-v5.patch, HBASE-22074-v6.patch, HBASE-22074-v7.patch, 
> HBASE-22074.patch
>
>
> For now we will update the meta region directly. This may cause lots of 
> problems and after a bunch of fixes, we still can not solve the problem in 
> HBASE-22060.
> So maybe the approach itself is not a good choice, let's try another way to 
> see if it could work better.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to