Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-5567 [Umbrella] Stabilize MR framework w.r.t ResourceManager restart
  3. MAPREDUCE-5505

Clients should be notified job finished only after job successfully unregistered

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • None
    • 2.2.0
    • None
    • None
    • Reviewed

    Description

      This is to make sure user is notified job finished after job is really done. This does increase client latency but can reduce some races during unregister like YARN-540

      Attachments

        1. MAPREDUCE-5505.1.patch
          7 kB
          Zhijie Shen
        2. MAPREDUCE-5505.1.patch
          7 kB
          Zhijie Shen
        3. MAPREDUCE-5505.3.patch
          14 kB
          Zhijie Shen
        4. MAPREDUCE-5505.4.patch
          27 kB
          Zhijie Shen
        5. MAPREDUCE-5505.5.patch
          32 kB
          Zhijie Shen
        6. MAPREDUCE-5505.6.patch
          17 kB
          Zhijie Shen
        7. MAPREDUCE-5505.7.patch
          19 kB
          Zhijie Shen

        Issue Links

        blocks

        New Feature - A new feature of the product, which has yet to be developed. YARN-128 [Umbrella] RM Restart Phase 1: State storage and non-work-preserving recovery

        • Major - Major loss of function.
        • Resolved
        breaks

        Sub-task - The sub-task of the issue MAPREDUCE-5538 MRAppMaster#shutDownJob shouldn't send job end notification before checking isLastRetry

        • Blocker - Blocks development and/or testing work, production could not run
        • Closed
        relates to

        Sub-task - The sub-task of the issue YARN-1195 RM may relaunch already KILLED / FAILED jobs after RM restarts

        • Major - Major loss of function.
        • Resolved

        Sub-task - The sub-task of the issue YARN-540 Race condition causing RM to potentially relaunch already unregistered AMs on RM restart

        • Major - Major loss of function.
        • Closed

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

          People

            zjshen Zhijie Shen
            jianhe Jian He
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment