You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "hongbin ma (JIRA)" <ji...@apache.org> on 2017/12/14 06:59:00 UTC

[jira] [Updated] (KYLIN-3106) DefaultScheduler.shutdown should use ExecutorService.shutdownNow instead of ExecutorService.shutdown

     [ https://issues.apache.org/jira/browse/KYLIN-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

hongbin ma updated KYLIN-3106:
------------------------------
    Summary: DefaultScheduler.shutdown should use ExecutorService.shutdownNow instead of ExecutorService.shutdown  (was: DefaultScheduler#shutdown should use shutdownNow instead of shutdown)

> DefaultScheduler.shutdown should use ExecutorService.shutdownNow instead of ExecutorService.shutdown
> ----------------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-3106
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3106
>             Project: Kylin
>          Issue Type: Bug
>            Reporter: hongbin ma
>             Fix For: v2.3.0
>
>
> java.util.concurrent.ExecutorService#shutdownNow will interrupt running worker threads, while java.util.concurrent.ExecutorService#shutdown will not.
> if interrupt signal is sent, a worker thread can get aware of it and abort itself in time. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)