Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-4685

Disable AM blacklisting by default to mitigate situations that application get hanged

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 2.8.0
    • 2.8.0, 3.0.0-alpha1
    • resourcemanager
    • None
    • Reviewed

    Description

      AM blacklist addition or removal is updated only when RMAppAttempt is scheduled i.e RMAppAttemptImpl#ScheduleTransition#transition. But once attempt is scheduled if there is any removeNode/addNode in cluster then this is not updated to BlackListManager#refreshNodeHostCount. This leads BlackListManager to operate on stale NM's count. And application is in ACCEPTED state and wait forever even if blacklisted nodes are reconnected with clearing disk space.

      Attachments

        Issue Links

        Activity

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

          People

            rohithsharma Rohith Sharma K S Assign to me
            rohithsharma Rohith Sharma K S
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment