[HBASE-5213] "hbase master stop" does not bring down backup masters

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.90.5, 0.92.0, 0.94.0, 0.95.2
• Fix Version/s: 0.94.0, 0.95.0
• Hadoop Flags: Reviewed
• Assignee: Gregory Chanan
• Reporter: Gregory Chanan
• Created: 17/Jan/12 02:38
• Updated: 09/May/13 22:40
• Resolved: 09/Apr/12 18:45

Description

Typing "hbase master stop" produces the following message:

"stop Start cluster shutdown; Master signals RegionServer shutdown"
It seems like backup masters should be considered part of the cluster, but they are not brought down by "hbase master stop".
"stop-hbase.sh" does correctly bring down the backup masters.

The same behavior is observed when a client app makes use of the client API HBaseAdmin.shutdown() http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HBaseAdmin.html#shutdown() – this isn't too surprising since I think "hbase master stop" just calls this API.

It seems like HBASE-1448 address this; perhaps there was a regression?

Issue Links

• relates to: HBASE-8519 Backup master will never come up if primary master dies during initialization

Sub-Tasks

• "hbase master stop" does not bring down backup masters: Closed