hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daisuke Kobayashi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12426) Dead Region Servers after Decommissioning
Date Fri, 15 Jan 2016 07:16:39 GMT

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

Daisuke Kobayashi commented on HBASE-12426:

[~nishanthshajahan], I came across this issue recently and such status has gone by restarting
HMaster (along with failover). Did you also restart the HMaster? 

> Dead Region Servers after Decommissioning 
> ------------------------------------------
>                 Key: HBASE-12426
>                 URL: https://issues.apache.org/jira/browse/HBASE-12426
>             Project: HBase
>          Issue Type: Bug
>          Components: Balancer
>    Affects Versions:
>         Environment: RHEL 6.5
>            Reporter: Nishanth Shajahan
>            Priority: Minor
> I initially had a set of  5 region servers  which had a single table  which was pre split
into 30 regions and was evenly distributed to all the regions with data.I then went ahead
and removed/decommissioned a coupe of region servers,so in the end I have 3 region servers.Ran
 hbase hbck and verified there were 0 inconsistencies.However when  'status' command is issued
is from  hbase shell it shows a dead region server and the same is displayed in master UI
as well.Fail over of hbase master did not fix the issue.On investigation we could see some
WAL entries which was still pointing to the old region server.
> /hbase/WALs/myserver,60020,1406745344969-splitting
> After removing these orphan entries from  hdfs and  master failover the dead region servers
went away.I wonder if this  could have  caused any replication issues in the cluster.

This message was sent by Atlassian JIRA

View raw message