[jira] [Updated] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-22121: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to branch-2.2+. Thanks [~zghaobac] for reviewing. > 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)
[jira] [Updated] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-22121: -- Fix Version/s: (was: 2.1.5) > 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)
[jira] [Updated] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-22121: -- Attachment: HBASE-22121.patch > 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, 2.1.5 > > 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)
[jira] [Updated] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-22121: -- Attachment: HBASE-22121.patch > 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, 2.1.5 > > Attachments: 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)
[jira] [Updated] (HBASE-22121) AsyncAdmin can not deal with non default meta replica
[ https://issues.apache.org/jira/browse/HBASE-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-22121: -- Status: Patch Available (was: Open) > 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, 2.1.5 > > Attachments: 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)
