hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14529) Respond to SIGHUP to reload config
Date Thu, 01 Oct 2015 23:46:26 GMT

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

Elliott Clark commented on HBASE-14529:

Disown is pretty close to nohup for our purposes.

nohup will mask out getting the SIGHUP signal. So java won't ever get the SIGHUP signal. We're
doing that so that when someone closes a login shell things aren't killed.
diswon does something different. It changes who the parent process is to 1 (init). That means
that when someone closes their shell the java process continues. However it doesn't filter
out the hup signal. So java can still get that sent.

For the user it should be seamless. They shouldn't see any difference other pstree will have
the java hanging off of init even before the users closes their shell.

> Respond to SIGHUP to reload config
> ----------------------------------
>                 Key: HBASE-14529
>                 URL: https://issues.apache.org/jira/browse/HBASE-14529
>             Project: HBase
>          Issue Type: New Feature
>    Affects Versions: 1.2.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>             Fix For: 2.0.0, 1.3.0
>         Attachments: HBASE-14529-v1.patch, HBASE-14529-v2.patch, HBASE-14529.patch
> SIGHUP is the way everyone since the dawn of unix has done config reload.
> Lets not be a special unique snowflake.

This message was sent by Atlassian JIRA

View raw message