Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
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).
Attachments
Issue Links
- is superceded by
-
FLINK-5114 PartitionState update with finished execution fails
- Closed