Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 27 Aug 2011 03:09:30 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1071689432.20324.1314414570290.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=13092174#comment-13092174 ] 

stack commented on HBASE-4209:
------------------------------

bq. suppressHdfsShutdownHook can't disable the HDFS shutdown hook of the miniDFS, simply because there's nothing to disable.

There is no hdfs shutdown hook when running minihdfs?

And I don't follow how testing for localfs helps.  I'm not clear on why testing for local fs makes a differenc when the shutdown hook is not in minidfs (?).  I'm missing something.

bq. I'd appreciate your advice, since I'm just learning my way around HBase.

You seem to be doing just fine to me.  Obviously from above exchange you know more about this area of the code than I do (and I think I wrote it?).  That suppressHdfsShutdownHook is really pretty (smile).  Thats some ugly gymnastics going on in there.


> 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