Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: scheduler
    • Labels:
      None

      Activity

      Hide
      NO NAME added a comment -

      The MR2 node update API already has hooks for the RM to tell the NM to release containers. Are there any problems using this method to preempt containers? I.e. will application masters handle unexpected container disruption gracefully or are there other considerations if we want the scheduler to preempt?

      Show
      NO NAME added a comment - The MR2 node update API already has hooks for the RM to tell the NM to release containers. Are there any problems using this method to preempt containers? I.e. will application masters handle unexpected container disruption gracefully or are there other considerations if we want the scheduler to preempt?
      Hide
      NO NAME added a comment -

      This patch adds preemption to the MR2 Fair Scheduler. It will not apply cleanly to trunk, instead depending on MAPREDUCE-3600 and MAPREDUCE-3601 patches already uploaded.

      Show
      NO NAME added a comment - This patch adds preemption to the MR2 Fair Scheduler. It will not apply cleanly to trunk, instead depending on MAPREDUCE-3600 and MAPREDUCE-3601 patches already uploaded.
      Hide
      NO NAME added a comment -

      Solved with parent ticket.

      Show
      NO NAME added a comment - Solved with parent ticket.

        People

        • Assignee:
          NO NAME
          Reporter:
          NO NAME
        • Votes:
          0 Vote for this issue
          Watchers:
          9 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development