hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4209) The HBase hbase-daemon.sh SIGKILLs master when stopping it
Date Wed, 17 Aug 2011 18:48:27 GMT

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

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

stack, before I submit the patch, I would really appreciate if you could let me know the relationship
between bin/stop-hbase.sh and bin/hbase-daemon.sh. I was under the impression that whatever
stop-hbase.sh triggers in the master code would also be triggered by JVM shutdown hook upon
receiving SIGTERM, but it doesn't seem to be that way. Do we have to call bin/stop-hbase.sh
manually from within the hbase-daemon.sh before stopping daemons?

> 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

        

Mime
View raw message