Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-4131

Confusing error for out dated RequestPartitionState

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

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

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            uce Ufuk Celebi
            uce Ufuk Celebi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment