[ https://issues.apache.org/jira/browse/FLINK-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899895#comment-16899895 ]
Biao Liu commented on FLINK-9845: --------------------------------- I think this issue should be reconsidered through mailbox thread model. > Make InternalTimerService's timer processing interruptible/abortable > -------------------------------------------------------------------- > > Key: FLINK-9845 > URL: https://issues.apache.org/jira/browse/FLINK-9845 > Project: Flink > Issue Type: Improvement > Components: Runtime / State Backends > Affects Versions: 1.5.1, 1.6.0 > Reporter: Till Rohrmann > Assignee: Biao Liu > Priority: Major > > When cancelling a {{Task}}, the task thread might currently process the > timers registered at the {{InternalTimerService}}. Depending on the timer > action, this might take a while and, thus, blocks the cancellation of the > {{Task}}. In the most extreme case, the {{TaskCancelerWatchDog}} kicks in and > kills the whole {{TaskManager}} process. > In order to alleviate the problem (speed up the cancellation reaction), we > should make the processing of the timers interruptible/abortable. This means > that instead of processing all timers we should check in between timers > whether the {{Task}} is currently being cancelled or not. If this is the > case, then we should directly stop processing the remaining timers and return. -- This message was sent by Atlassian JIRA (v7.6.14#76016)