[
https://issues.apache.org/jira/browse/FLINK-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-9845:
----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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
> Priority: Major
> Labels: auto-unassigned, stale-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
(v8.3.4#803005)
