You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2018/03/05 00:49:00 UTC
[jira] [Created] (FLINK-8856) Move all interrupt() calls to
TaskCanceler
Stephan Ewen created FLINK-8856:
-----------------------------------
Summary: Move all interrupt() calls to TaskCanceler
Key: FLINK-8856
URL: https://issues.apache.org/jira/browse/FLINK-8856
Project: Flink
Issue Type: Bug
Components: TaskManager
Reporter: Stephan Ewen
Fix For: 1.5.0
We need this to work around the following JVM bug: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8138622
To circumvent this problem, the {{TaskCancelerWatchDog}} must not call {{interrupt()}} at all, but only join on the executing thread (with timeout) and cause a hard exit once cancellation takes to long.
A user affected by this problem reported this in FLINK-8834
Personal note: The Thread.join(...) method unfortunately is not 100% reliable as well, because it uses {{System.currentTimeMillis()}} rather than {{System.nanoTime()}}. Because of that, sleeps can take overly long when the clock is adjusted. I wonder why the JDK authors do not follow their own recommendations and use {{System.nanoTime()}} for all relative time measures...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)