[
https://issues.apache.org/jira/browse/TAJO-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738312#comment-14738312
]
ASF GitHub Bot commented on TAJO-1831:
--------------------------------------
GitHub user jinossy opened a pull request:
https://github.com/apache/tajo/pull/751
TAJO-1831: Add a shutdown hook manager in order to set priorities.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jinossy/tajo TAJO-1831
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/751.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #751
----
commit 16c556034c58174e8eb678974e453078daab5472
Author: Jinho Kim <[email protected]>
Date: 2015-09-10T07:21:11Z
TAJO-1831: Add a shutdown hook manager in order to set priorities.
----
> Add a shutdown hook manager in order to set priorities
> ------------------------------------------------------
>
> Key: TAJO-1831
> URL: https://issues.apache.org/jira/browse/TAJO-1831
> Project: Tajo
> Issue Type: Improvement
> Components: Java Client, RPC, TajoMaster, Worker
> Reporter: Jinho Kim
> Assignee: Jinho Kim
> Priority: Minor
>
> Sometimes, event-group thread of netty’s is not stopped. because jvm will
> start a shutdown-hook after all thread is stopped without kill signal. it is
> dead-lock state.
> We should explicitly call to shutdown the event-group thread of netty’s and
> should set a shutdown-hook order
> For example, before you start up TajoMaster, runs tsql, you can find deadlock
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
