[
https://issues.apache.org/jira/browse/KYLIN-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830888#comment-17830888
]
pengfei.zhan commented on KYLIN-5759:
-------------------------------------
h1. Design
this method _{{ExecutableContext#addRunningJob}}_ will be separated from the
current thread (runningJobThreads.put(executable.getId(),
Thread.currentThread())) . The purpose of this is that {{_addRunningJob_}} is
just a record of which tasks have been scheduled, used to determine the
subsequent do not be repeated scheduling, this should not add the current
thread (scheduling thread), but in the task is actually executed when the
current thread add.
> Modify "ExecutableContext#addRunningJob" to avoid schedule job more than once
> -----------------------------------------------------------------------------
>
> Key: KYLIN-5759
> URL: https://issues.apache.org/jira/browse/KYLIN-5759
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
> Affects Versions: 5.0-beta
> Reporter: pengfei.zhan
> Assignee: pengfei.zhan
> Priority: Major
> Fix For: 5.0-beta
>
>
> When a task is scheduled, the task is logged into runningJobs and the current
> thread is logged into runningJobThreads, which is expected to be the thread
> that executes the task, but in fact it is the scheduler's thread that is
> logged, which results in subsequent attempts to interrupt the scheduler
> FetcherRunner when killing the task.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
