[
https://issues.apache.org/jira/browse/HBASE-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-3590:
-------------------------
Issue Type: New Feature (was: Bug)
Its a feature because from the original mail thread:
{code}
> So the question is, is this a bug or a feature? If it's a feature it
> seems like an incredibly dangerous one. Once our live cluster is
> running, those configs will also be needed on the client so really bad
> things could happen by mistake.
>
One time it might have been thought a 'feature' but now its a bug I'd
say given the above.
{code}
> stop-hbase.sh stopping the cluster can catch folks by surprise, in a bad way!
> -----------------------------------------------------------------------------
>
> Key: HBASE-3590
> URL: https://issues.apache.org/jira/browse/HBASE-3590
> Project: HBase
> Issue Type: New Feature
> Reporter: stack
>
> See
> http://search-hadoop.com/m/2LZVV1IOPbL/stop-hbase.sh+bug+or+feature%253F&subj=stop+hbase+sh+bug+or+feature+
> for context. stop-hbase.sh will happily stop the whole cluster, even the
> remote production one. Remove or add in safeguard.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
