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

RM should handle NMContainerStatuses sent by NM while registering if NM is Reconnected node

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


    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 2.7.0
    • 2.7.0, 2.6.2, 3.0.0-alpha1
    • resourcemanager
    • None
    • NM restart is enabled

    • Reviewed


      On NM restart ,NM sends all the outstanding NMContainerStatus to RM during registration. The registration can be treated by RM as New node or Reconnecting node. RM triggers corresponding event on the basis of node added or node reconnected state.

      1. Node added event : Again here 2 scenario's can occur
        1. New node is registering with different ip:port – NOT A PROBLEM
        2. Old node is re-registering because of RESYNC command from RM when RM restart – NOT A PROBLEM
      1. Node reconnected event :
        1. Existing node is re-registering i.e RM treat it as reconnecting node when RM is not restarted
          1. NM RESTART NOT Enabled – NOT A PROBLEM
          2. NM RESTART is Enabled
            1. Some applications are running on this node – Problem is here
            2. Zero applications are running on this node – NOT A PROBLEM

      Since NMContainerStatus are not handled, RM never get to know about completedContainer and never release resource held be containers. RM will not allocate new containers for pending resource request as long as the completedContainer event is triggered. This results in applications to wait indefinitly because of pending containers are not served by RM.



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


            rohithsharma Rohith Sharma K S Assign to me
            rohithsharma Rohith Sharma K S
            0 Vote for this issue
            8 Start watching this issue




                Issue deployment