[
https://issues.apache.org/jira/browse/HBASE-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248416#comment-13248416
]
David S. Wang commented on HBASE-5213:
--------------------------------------
Greg is out of town for the next week or so ... IMHO if it's breaking 0.90, we
should revert for now and Greg can look at it when he gets back.
> "hbase master stop" does not bring down backup masters
> ------------------------------------------------------
>
> Key: HBASE-5213
> URL: https://issues.apache.org/jira/browse/HBASE-5213
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.5, 0.92.0, 0.94.0, 0.96.0
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Priority: Minor
> Fix For: 0.90.7, 0.92.2, 0.94.0, 0.96.0
>
> Attachments: HBASE-5213-v0-trunk.patch, HBASE-5213-v1-trunk.patch,
> HBASE-5213-v2-90.patch, HBASE-5213-v2-92.patch, HBASE-5213-v2-trunk.patch
>
>
> 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?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
