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

Hudson commented on HBASE-22121:
--------------------------------

Results for branch branch-2.2
        [build #144 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/144/]: 
(x) *{color:red}-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.2/144//General_Nightly_Build_Report/]




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


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


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


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


> AsyncAdmin can not deal with non default meta replica
> -----------------------------------------------------
>
>                 Key: HBASE-22121
>                 URL: https://issues.apache.org/jira/browse/HBASE-22121
>             Project: HBase
>          Issue Type: Bug
>          Components: Admin, asyncclient, Client
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.3.0
>
>         Attachments: HBASE-22121.patch, HBASE-22121.patch
>
>
> In AsyncAdmin we support passing both encodedRegionName and regionName as a 
> parameter so we have a getRegionInfo method to get the RegionInfo first.
> In general we will scan the meta table to get the region info, but for meta 
> region itself, the problem is that, we only check for the first replica, so 
> for the non default replicas, we will still go to the meta region and then 
> get an UnknownRegionException.
> We should find a way to deal with this.



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

Reply via email to