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

Job with -m yarn-cluster registers TaskManagers to another running Yarn session

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

    Details

      Description

      When a job is started using cluster mode (-m yarn-cluster) and a Yarn session is running on the same cluster, the job accidentally registers it's worker tasks with the ongoing Yarn session. This happens because the same Zookeeper namespace is used.

      We should consider isolating Flink applications from another by using UUIDS, e.g. based on their application ids, in their Zookeeper paths.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              srichter Stefan Richter

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment