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

Hudson commented on HBASE-20378:
--------------------------------

Results for branch branch-2
        [build #694 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/694/]: 
(/) *{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/694//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/694//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/694//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


> Provide a hbck option to cleanup replication barrier for a table
> ----------------------------------------------------------------
>
>                 Key: HBASE-20378
>                 URL: https://issues.apache.org/jira/browse/HBASE-20378
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 3.0.0
>            Reporter: Duo Zhang
>            Assignee: Jingyun Tian
>            Priority: Major
>             Fix For: 3.0.0, 2.1.0
>
>         Attachments: HBASE-20378.master.001.patch, 
> HBASE-20378.master.002.patch, HBASE-20378.master.003.patch, 
> HBASE-20378.master.004.patch, HBASE-20378.master.005.patch, 
> HBASE-20378.master.006.patch, HBASE-20378.master.007.patch, 
> HBASE-20378.master.008.patch
>
>
> It is not easy to deal with the scenario where a user change the replication 
> scope from global to local since it may change the scope back while we are 
> cleaning in the background. And I think this a rare operation so just provide 
> an hbck option to deal with it.



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

Reply via email to