Hadoop YARN
  1. Hadoop YARN
  2. YARN-443

allow OS scheduling priority of NM to be different than the containers it launches

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.3-alpha, 0.23.6
    • Fix Version/s: 0.23.7, 2.0.4-alpha
    • Component/s: nodemanager
    • Labels:
      None

      Description

      It would be nice if we could have the nodemanager run at a different OS scheduling priority than the containers so that you can still communicate with the nodemanager if the containers out of control.

      On linux we could launch the nodemanager at a higher priority, but then all the containers it launches would also be at that higher priority, so we need a way for the container executor to launch them at a lower priority.

      I'm not sure how this applies to windows if at all.

      1. YARN-443.patch
        15 kB
        Thomas Graves
      2. YARN-443.patch
        15 kB
        Thomas Graves
      3. YARN-443.patch
        15 kB
        Thomas Graves
      4. YARN-443.patch
        14 kB
        Thomas Graves
      5. YARN-443.patch
        8 kB
        Thomas Graves
      6. YARN-443.patch
        6 kB
        Thomas Graves
      7. YARN-443.patch
        5 kB
        Thomas Graves
      8. YARN-443-branch-0.23.patch
        13 kB
        Thomas Graves
      9. YARN-443-branch-0.23.patch
        13 kB
        Thomas Graves
      10. YARN-443-branch-0.23.patch
        7 kB
        Thomas Graves
      11. YARN-443-branch-0.23.patch
        6 kB
        Thomas Graves
      12. YARN-443-branch-2.patch
        11 kB
        Thomas Graves
      13. YARN-443-branch-2.patch
        10 kB
        Thomas Graves
      14. YARN-443-branch-2.patch
        7 kB
        Thomas Graves

        Issue Links

          Activity

          Thomas Graves created issue -
          Bikas Saha made changes -
          Field Original Value New Value
          Summary allow OS scheduling priority of NM to be different then the containers it launches allow OS scheduling priority of NM to be different than the containers it launches
          Bikas Saha made changes -
          Description It would be nice if we could have the nodemanager run at a different OS scheduling priority then the containers so that you can still communicate with the nodemanager if the containers out of control.

          On linux we could launch the nodemanager at a higher priority, but then all the containers it launches would also be at that higher priority, so we need a way for the container executor to launch them at a lower priority.

          I'm not sure how this applies to windows if at all.
          It would be nice if we could have the nodemanager run at a different OS scheduling priority than the containers so that you can still communicate with the nodemanager if the containers out of control.

          On linux we could launch the nodemanager at a higher priority, but then all the containers it launches would also be at that higher priority, so we need a way for the container executor to launch them at a lower priority.

          I'm not sure how this applies to windows if at all.
          Thomas Graves made changes -
          Attachment YARN-443.patch [ 12572244 ]
          Thomas Graves made changes -
          Attachment YARN-443.patch [ 12572384 ]
          Thomas Graves made changes -
          Attachment YARN-443.patch [ 12572484 ]
          Thomas Graves made changes -
          Attachment YARN-443.patch [ 12572484 ]
          Thomas Graves made changes -
          Attachment YARN-443-branch-0.23.patch [ 12572486 ]
          Thomas Graves made changes -
          Attachment YARN-443-branch-0.23.patch [ 12572546 ]
          Attachment YARN-443-branch-2.patch [ 12572547 ]
          Thomas Graves made changes -
          Attachment YARN-443.patch [ 12572548 ]
          Thomas Graves made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Thomas Graves made changes -
          Attachment YARN-443.patch [ 12572561 ]
          Thomas Graves made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Thomas Graves made changes -
          Attachment YARN-443-branch-0.23.patch [ 12572595 ]
          Attachment YARN-443-branch-2.patch [ 12572596 ]
          Thomas Graves made changes -
          Attachment YARN-443.patch [ 12572597 ]
          Thomas Graves made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Thomas Graves made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Thomas Graves made changes -
          Attachment YARN-443-branch-0.23.patch [ 12572600 ]
          Attachment YARN-443-branch-2.patch [ 12572601 ]
          Thomas Graves made changes -
          Attachment YARN-443.patch [ 12572602 ]
          Thomas Graves made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Thomas Graves made changes -
          Attachment YARN-443.patch [ 12572619 ]
          Thomas Graves made changes -
          Status Patch Available [ 10002 ] Resolved [ 5 ]
          Fix Version/s 0.23.7 [ 12323953 ]
          Fix Version/s 2.0.4-alpha [ 12324137 ]
          Fix Version/s 3.0.0 [ 12323268 ]
          Resolution Fixed [ 1 ]
          Allen Wittenauer made changes -
          Link This issue is related to MAPREDUCE-4058 [ MAPREDUCE-4058 ]
          Arun C Murthy made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Allen Wittenauer made changes -
          Fix Version/s 3.0.0 [ 12323268 ]

            People

            • Assignee:
              Thomas Graves
              Reporter:
              Thomas Graves
            • Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development