You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2016/06/29 11:47:37 UTC
[jira] [Created] (FLINK-4131) Confusing error for out dated
RequestPartitionState
Ufuk Celebi created FLINK-4131:
----------------------------------
Summary: Confusing error for out dated RequestPartitionState
Key: FLINK-4131
URL: https://issues.apache.org/jira/browse/FLINK-4131
Project: Flink
Issue Type: Improvement
Reporter: Ufuk Celebi
Assignee: Ufuk Celebi
When a consumer requests a partition state for an old job or execution attempt (e.g. failed job or attempt), the JobManager answers with a {{null}} state, which fails the requesting task with the following cause: {{IllegalStateException("Received unexpected partition state null for partition request. This is a bug.")}}.
This is confusing to the user as one might think that this is the root failure cause.
I propose to either ignore the null state at the Task or not respond on the JobManager side if the job or execution attempt has been cleared (see {{RequestPartitionState}} in {{JobManager.scala}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)