You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/04/11 02:38:13 UTC

[jira] [Resolved] (HBASE-1667) hbase-daemon.sh stop master should only stop the master, not the cluster

     [ https://issues.apache.org/jira/browse/HBASE-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell resolved HBASE-1667.
-----------------------------------
    Resolution: Not A Problem

> hbase-daemon.sh stop master should only stop the master, not the cluster
> ------------------------------------------------------------------------
>
>                 Key: HBASE-1667
>                 URL: https://issues.apache.org/jira/browse/HBASE-1667
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, scripts
>    Affects Versions: 0.20.0
>            Reporter: Rong-En Fan
>
> 0.20 supports multi masters. However,
> bin/hbase-daemon.sh stop master
> on backup masters will bring the whole cluster down.
> Per rolling upgrade wiki that stack pointed out, kill -9 for backup master is the only way to go currently.
> I think it's better to make some sort of magic that we can use something like
> bin/hbase-daemon.sh stop master
> to properly stop either the backup master or the whole cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)