hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akash Ashok (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4008) Problem while stopping HBase
Date Fri, 15 Jul 2011 17:57:59 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066098#comment-13066098

Akash Ashok commented on HBASE-4008:

I have a question regarding the standalone HBase which might not be a real world scenario
but fixing this issue I need to know what the behaviour should be after the fix. So for a
standalone HBase setup if the HMaster throws a severe exception and master doesn't come up
then HBase doesn't stop and goes to an inconsistent. 

In the case of True Distributed Mode only HMaster goes down as it runs on a separate JVM.

But how about a standalone case where exiting the JVM causes the RegionServer threads also
to be terminated ? In such a case master fails whole standalone HBase setup goes down. This
makes logical sense as its a single node setup. Just wanted to clarify if this is ok. 

> Problem while stopping HBase
> ----------------------------
>                 Key: HBASE-4008
>                 URL: https://issues.apache.org/jira/browse/HBASE-4008
>             Project: HBase
>          Issue Type: Bug
>          Components: scripts
>            Reporter: Akash Ashok
>            Assignee: Akash Ashok
> stop-hbase.sh stops the server successfully if and only if the server is instantiated
> When u Run 
> start-hbase.sh; sleep 10; stop-hbase.sh; ( This works totally fine and has no issues
> Whereas when u run 
> start-hbase.sh; stop-hbase.sh; ( This never stops the server and neither the server gets
initialized and starts properly )

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message