[HBASE-3580] Remove RS from DeadServer when new instance checks in

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.90.0
• Fix Version/s: 0.90.3
• Hadoop Flags: Reviewed
• Assignee: Jean-Daniel Cryans
• Reporter: Jean-Daniel Cryans
• Created: 28/Feb/11 18:15
• Updated: 20/Nov/15 12:41
• Resolved: 20/Apr/11 22:00

Description

Keeping the servers in DeadServer until it reaches some maximum isn't super friendly, it confuses even the best of our users:

09:27 < gbowyer> Hi all, I have apparently three dead RS in my cluster, I cannot find references to them in HDFS or in ZK, how do I still report dead RS
09:27 < gbowyer> also the same nodes are reported as live region servers

The subtil startcode difference can be hard to catch, also this behavior differs from 0.20 (so old users get confused, like I did when debugging this problem) and it also differs from Hadoop's handling of dead DataNodes. It was introduced in HBASE-3282.

I think this should be improved by doing like Hadoop does, removing the RS from DeadServers when a new instance with the same hostname+port checks in. Stack says we should do it in ServerManager.checkIsDead

Issue Links

• relates to: HBASE-4359 Show dead RegionServer names in the HMaster info page