[jira] [Updated] (HBASE-27651) hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
[
https://issues.apache.org/jira/browse/HBASE-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-27651:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the reviews.
> hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
>
>
> Key: HBASE-27651
> URL: https://issues.apache.org/jira/browse/HBASE-27651
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Minor
> Fix For: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>
>
> Running HBase in a container environment, launched using
> {{{}bin/hbase-daemon.sh foreground_start ...{}}}. Signaling the container for
> config refresh or for graceful termination doesn't make it through to the JVM
> process. Rather, the {{trap}} function is unconditionally sending {{{}kill
> -9{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27651) hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
[
https://issues.apache.org/jira/browse/HBASE-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-27651:
-
Fix Version/s: 2.4.17
> hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
>
>
> Key: HBASE-27651
> URL: https://issues.apache.org/jira/browse/HBASE-27651
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Minor
> Fix For: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>
>
> Running HBase in a container environment, launched using
> {{{}bin/hbase-daemon.sh foreground_start ...{}}}. Signaling the container for
> config refresh or for graceful termination doesn't make it through to the JVM
> process. Rather, the {{trap}} function is unconditionally sending {{{}kill
> -9{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27651) hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
[
https://issues.apache.org/jira/browse/HBASE-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-27651:
-
Fix Version/s: 2.5.4
> hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
>
>
> Key: HBASE-27651
> URL: https://issues.apache.org/jira/browse/HBASE-27651
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Minor
> Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.4
>
>
> Running HBase in a container environment, launched using
> {{{}bin/hbase-daemon.sh foreground_start ...{}}}. Signaling the container for
> config refresh or for graceful termination doesn't make it through to the JVM
> process. Rather, the {{trap}} function is unconditionally sending {{{}kill
> -9{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27651) hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
[
https://issues.apache.org/jira/browse/HBASE-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-27651:
-
Fix Version/s: 2.6.0
> hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
>
>
> Key: HBASE-27651
> URL: https://issues.apache.org/jira/browse/HBASE-27651
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Minor
> Fix For: 2.6.0, 3.0.0-alpha-4
>
>
> Running HBase in a container environment, launched using
> {{{}bin/hbase-daemon.sh foreground_start ...{}}}. Signaling the container for
> config refresh or for graceful termination doesn't make it through to the JVM
> process. Rather, the {{trap}} function is unconditionally sending {{{}kill
> -9{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27651) hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
[
https://issues.apache.org/jira/browse/HBASE-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-27651:
-
Fix Version/s: 3.0.0-alpha-4
> hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
>
>
> Key: HBASE-27651
> URL: https://issues.apache.org/jira/browse/HBASE-27651
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Minor
> Fix For: 3.0.0-alpha-4
>
>
> Running HBase in a container environment, launched using
> {{{}bin/hbase-daemon.sh foreground_start ...{}}}. Signaling the container for
> config refresh or for graceful termination doesn't make it through to the JVM
> process. Rather, the {{trap}} function is unconditionally sending {{{}kill
> -9{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27651) hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
[
https://issues.apache.org/jira/browse/HBASE-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-27651:
-
Release Note:
Introduce separate `trap`s for SIGHUP vs. the rest. Treat `SIGINT`, `SIGKILL`,
and `EXIT` identically, as before. Use the signal name without `SIG` prefix for
increased portability, as per the POSIX man page for `trap`.
`SIGTERM` handler will now honor `HBASE_STOP_TIMEOUT` as described in the file
header.
> hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
>
>
> Key: HBASE-27651
> URL: https://issues.apache.org/jira/browse/HBASE-27651
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Minor
>
> Running HBase in a container environment, launched using
> {{{}bin/hbase-daemon.sh foreground_start ...{}}}. Signaling the container for
> config refresh or for graceful termination doesn't make it through to the JVM
> process. Rather, the {{trap}} function is unconditionally sending {{{}kill
> -9{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27651) hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
[
https://issues.apache.org/jira/browse/HBASE-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-27651:
-
Affects Version/s: 2.6.0
3.0.0-alpha-4
2.4.17
2.5.4
Assignee: Nick Dimiduk
Status: Patch Available (was: Open)
> hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
>
>
> Key: HBASE-27651
> URL: https://issues.apache.org/jira/browse/HBASE-27651
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Minor
>
> Running HBase in a container environment, launched using
> {{{}bin/hbase-daemon.sh foreground_start ...{}}}. Signaling the container for
> config refresh or for graceful termination doesn't make it through to the JVM
> process. Rather, the {{trap}} function is unconditionally sending {{{}kill
> -9{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27651) hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
[
https://issues.apache.org/jira/browse/HBASE-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-27651:
-
Summary: hbase-daemon.sh foreground_start should propagate SIGHUP and
SIGTERM (was: hbase-daemon.sh foreground_start does not propagate SIGHUP or
SIGTERM properly)
> hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM
>
>
> Key: HBASE-27651
> URL: https://issues.apache.org/jira/browse/HBASE-27651
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Reporter: Nick Dimiduk
>Priority: Minor
>
> Running HBase in a container environment, launched using
> {{{}bin/hbase-daemon.sh foreground_start ...{}}}. Signaling the container for
> config refresh or for graceful termination doesn't make it through to the JVM
> process. Rather, the {{trap}} function is unconditionally sending {{{}kill
> -9{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
