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

Viraj Jasani commented on HBASE-22923:
--------------------------------------

{quote}Is this a config we will provide as part of our hbase default config xml?
{quote}
So far, have not yet put it in default config because this is totally optional 
(mostly applicable to RSGroup feature, and since it is not enabled by default, 
I have not included in hbase-default also).
{quote}So when the migrate version > this min version, user need to 1st upgrade 
RS assigned with System RS group?
{quote}
That's right [~anoop.hbase].
{quote}If there is only 1 RS in system group and when the upgrade is happening, 
the System table regions will get moved to default or any other RS group's RS?
{quote}
Having only single RS in system RSGroup will never be helpful because regions 
that belong to particular RSGroup can never be assigned to another RSGroup, and 
that's what we are trying to prevent by adding config (because AM cannot access 
RSGroup APIs directly, RSGroupInfoManager is part of hbase-rsgroup module which 
is not accessible to hbase-server in branch-1 and branch-2). But it is for 
certain that regardless of how small any RSGroup is, we should definitely have 
more than 1 RS for all RSGroups, otherwise during rolling restarts, regions 
will not be moved to any server.

> hbase:meta is assigned to localhost when we downgrade the hbase version
> -----------------------------------------------------------------------
>
>                 Key: HBASE-22923
>                 URL: https://issues.apache.org/jira/browse/HBASE-22923
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.4.8
>            Reporter: wenbang
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0, 2.3.6, 1.7.1, 2.4.5
>
>
> When we downgrade the hbase version(rsgroup enable), we found that the 
> hbase:meta table could not be assigned.
> {code:java}
> master.AssignmentManager: Failed assignment of hbase:meta,,1.1588230740 to 
> localhost,1,1, trying to assign elsewhere instead; try=1 of 10 
> java.io.IOException: Call to localhost/127.0.0.1:1 failed on local exception: 
> org.apache.hadoop.hbase.ipc.FailedServerException: This server is in the 
> failed servers list: localhost/127.0.0.1:1
> {code}
> hbase group list:
>   HBASE_META group(hbase:meta and other system tables)
>   default group
> 1.Down grade all servers in HBASE_META first
> 2.higher version servers is in default
> 3.hbase:meta assigned to localhost
> For system table, we assign them to a server with highest version.
> AssignmentManager#getExcludedServersForSystemTable
> But did not consider the rsgroup.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to