You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Billy Liu (JIRA)" <ji...@apache.org> on 2018/01/24 08:52:00 UTC
[jira] [Resolved] (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 ]
Billy Liu resolved KYLIN-3106.
------------------------------
Resolution: Fixed
Commit: http://git-wip-us.apache.org/repos/asf/kylin/commit/f2722eb7
> 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
> Components: Job Engine
> Reporter: hongbin ma
> Assignee: hongbin ma
> Priority: Major
> 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
(v7.6.3#76005)