[
https://issues.apache.org/jira/browse/HBASE-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091246#comment-13091246
]
Roman Shaposhnik commented on HBASE-4209:
-----------------------------------------
stack, I have tried it with a standalone HBase writing to a local filesystem (I
think there's no way making a standalone instance of HBase use HDFS). And that
works quite nicely. Tables get flushed when I SIGTERM the process, etc. Once it
came to testing I had to run it with miniDFS and that's where things got
interesting. suppressHdfsShutdownHook can't disable the HDFS shutdown hook of
the miniDFS, simply because there's nothing to disable.
So here's the question, should I work around this one special case by simply
testing for the
{noformat}
LocalHBaseCluster.isLocal(hrs.getConfiguration())
{noformat}
or would you propose something else?
I'd appreciate your advice, since I'm just learning my way around HBase.
> 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
