[
https://issues.apache.org/jira/browse/IMPALA-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823315#comment-16823315
]
Bikramjeet Vig commented on IMPALA-8401:
----------------------------------------
SIGRTMIN was used instead of SIGQUIT because it is already used by JVM to dump
Java stack traces. See
[here|https://docs.oracle.com/javase/10/troubleshoot/handle-signals-and-exceptions.htm#JSTGD356]
> Initiate graceful shutdown of impala daemon by sending a signal to the process
> ------------------------------------------------------------------------------
>
> Key: IMPALA-8401
> URL: https://issues.apache.org/jira/browse/IMPALA-8401
> Project: IMPALA
> Issue Type: Bug
> Reporter: Bikramjeet Vig
> Assignee: Bikramjeet Vig
> Priority: Major
> Fix For: Impala 3.3.0
>
>
> Once the shut down process is initiated, impalad would stop accepting any new
> connections or queries. This makes it difficult if a user wants to shut down
> impalad across a cluster via the shutdown command. For eg. the user would
> need to make sure to send the command to all executors before sending them to
> the coordinators. Adding a mechanism to initiate the graceful shutdown
> process with a large deadline by sending a SIGRTMIN to the impalad process
> would make cluster management simpler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
