Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-5597 YARN Federation improvements
  3. YARN-8980

Mapreduce application container start fail after AM restart.

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersStop watchingWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Reviewed

    Description

      UAM to subclusters are always launched with keepContainers.

      On AM restart scenarios , UAM register again with RM . UAM receive running containers with NMToken. NMToken received by UAM in getPreviousAttemptContainersNMToken is never used by mapreduce application.

      Federation Interceptor should take care of such scenarios too. Merge NMToken received at registration to allocate response.

      Container allocation response on same node will have NMToken empty.

      issue credits : Nallasivan

      Attachments

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

          People

            zhengchenyu Chenyu Zheng Assign to me
            bibinchundatt Bibin Chundatt
            Votes:
            0 Vote for this issue
            Watchers:
            5 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment