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

Non-AM containers can be counted towards amResourceUsage of a Fair Scheduler queue

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 2.6.0
    • 2.8.0, 3.0.0-alpha1
    • fairscheduler
    • None
    • Reviewed

    Description

      We encountered this problem while running a spark cluster. The amResourceUsage for a queue became artificially high and then the cluster got deadlocked because the maxAMShare constrain kicked in and no new AM got admitted to the cluster.

      I have described the problem in detail here: https://github.com/apache/spark/pull/5233#issuecomment-87160289

      In summary - the condition for adding the container's memory towards amResourceUsage is fragile. It depends on the number of live containers belonging to the app. We saw that the spark AM went down without explicitly releasing its requested containers and then one of those containers memory was counted towards amResource.

      cc - Sandy Ryza

      Attachments

        1. YARN-3415.000.patch
          7 kB
          Zhihai Xu
        2. YARN-3415.001.patch
          12 kB
          Zhihai Xu
        3. YARN-3415.002.patch
          12 kB
          Zhihai Xu

        Activity

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

          People

            zxu Zhihai Xu
            ragarwal Rohit Agarwal
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment