Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 10 Sep 2011 00:16:08 +0000 (UTC)
From: "Roman Shaposhnik (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <82346087.10569.1315613768930.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <65750022.42864.1313531007186.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4209) The HBase hbase-daemon.sh SIGKILLs
 master when stopping it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Roman Shaposhnik commented on HBASE-4209:
-----------------------------------------

stack, I'm sorry for putting this on a backburner, but at least I now have a better understanding of what's going on. 

Basically I got confused in a situation where suppressHdfsShutdownHook would be called multiple times on the same filesystem object. The first call would succeed, but all the other ones would fail. This is, obviously, just a problem with my patch, not the minihdfs cluster. I'll cook up an alternative and once I run the tests will attach an updated version.

P.S. Thanks for the encouragement!

> The HBase hbase-daemon.sh SIGKILLs master when stopping it
> ----------------------------------------------------------
>
>                 Key: HBASE-4209
>                 URL: https://issues.apache.org/jira/browse/HBASE-4209
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Roman Shaposhnik
>
> There's a bit of code in hbase-daemon.sh that makes HBase master being SIGKILLed when stopping it rather than trying SIGTERM (like it does for other daemons). When HBase is executed in a standalone mode (and the only daemon you need to run is master) that causes newly created tables to go missing as unflushed data is thrown out. If there was not a good reason to kill master with SIGKILL perhaps we can take that special case out and rely on SIGTERM.

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