[
https://issues.apache.org/jira/browse/FLINK-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325695#comment-14325695
]
Ufuk Celebi commented on FLINK-1577:
------------------------------------
{code}
10:56:40,161 ERROR org.apache.flink.runtime.execution.RuntimeEnvironment
- Error during running invokable: Event handler interrupted without reaching
end-of-superstep.
java.lang.RuntimeException: Event handler interrupted without reaching
end-of-superstep.
{code}
{code}
10:56:40,197 ERROR org.apache.flink.runtime.execution.RuntimeEnvironment
- Error during running invokable: Bug in reader logic: queried for a buffer
although none was available.
java.lang.IllegalStateException: Bug in reader logic: queried for a buffer
although none was available.
at
org.apache.flink.runtime.io.network.api.reader.BufferReader.getNextBufferBlocking(BufferReader.java:267)
{code}
> Misleading error messages when cancelling tasks
> -----------------------------------------------
>
> Key: FLINK-1577
> URL: https://issues.apache.org/jira/browse/FLINK-1577
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Runtime
> Affects Versions: master
> Reporter: Ufuk Celebi
>
> A user running a Flink version before bec9c4d ran into a job manager failure
> (fixed in bec9c4d), which lead to restarting the JM and cancelling/clearing
> all tasks on the TMs.
> The logs of the TMs were inconclusive. I think part of that has been fixed by
> now, e.g. there is a log message when cancelAndClearEverything is called, but
> the task thread (RuntimeEnvironment) always logs an error when interrupted
> during the run method -- even if the task gets cancelled.
> I think these error messages are misleading and only the root cause is
> important (i.e. non-failed tasks should be silently cancelled).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
