[HBASE-27651] hbase-daemon.sh foreground_start should propagate SIGHUP and SIGTERM - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
Fix Version/s: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
Component/s: scripts
Labels:
None

Release Note:

Hide

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.

Show
 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.

Description

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.