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

Xiaolin Ha commented on HBASE-19326:
------------------------------------

[~andrewcheng][~stack]
In docs it said that 'The default group is not like other rsgroups in that it 
is dynamic. Its server list mirrors the current
state of the cluster; i.e. if you shutdown a server that was part of the 
default rsgroup, and then do a
get_rsgroup default to list its content in the shell, the server will no longer 
be listed. For non-default
groups, though a mode may be offline, it will persist in the non-default 
group’s list of servers. But if
you move the offline server from the non-default rsgroup to default, it will 
not show in the default
list. It will just be dropped.'

But when a regionserver is dead and master is restarted, the regionserver can 
be removed from the non-default rsgroup too.
Is this conflict with the doc? Do you think dead regionservers can be removed 
either?



> Remove decommissioned servers from rsgroup
> ------------------------------------------
>
>                 Key: HBASE-19326
>                 URL: https://issues.apache.org/jira/browse/HBASE-19326
>             Project: HBase
>          Issue Type: New Feature
>          Components: rsgroup
>    Affects Versions: 3.0.0, 2.0.0-beta-2
>            Reporter: Guangxu Cheng
>            Assignee: Guangxu Cheng
>            Priority: Major
>             Fix For: 1.4.0, 2.0.0-beta-1
>
>         Attachments: HBASE-19326-branch-1.patch, 
> HBASE-19326.branch-2.001.patch, HBASE-19326.master.001.patch, 
> HBASE-19326.master.002.patch, HBASE-19326.master.003.patch, 
> HBASE-19326.master.004.patch, HBASE-19326.master.005.patch
>
>
> In HBASE-18131, we add an hbase shell command {{clear_deadservers}} to clear 
> deadserver list in ServerManager.
> But rsgroup still contains these dead servers, so we should also remove dead 
> servers from the group information.



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

Reply via email to