Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0, 3.0.0-alpha1
    • Component/s: resourcemanager
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      Currently ApplicationClientProtocol#updateApplicationPriority() API returns empty UpdateApplicationPriorityResponse response.
      But RM update priority to the cluster.max-priority if the given priority is greater than cluster.max-priority. In this scenarios, need to intimate back to client that updated priority rather just keeping quite where client assumes that given priority itself is taken.

      During application submission also has same scenario can happen, but I feel when
      explicitly invoke via ApplicationClientProtocol#updateApplicationPriority(), response should have updated priority in response.

        Attachments

        1. 0004-YARN-4164.patch
          17 kB
          Rohith Sharma K S
        2. 0003-YARN-4164.patch
          17 kB
          Rohith Sharma K S
        3. 0002-YARN-4164.patch
          16 kB
          Rohith Sharma K S
        4. 0001-YARN-4164.patch
          16 kB
          Rohith Sharma K S

          Activity

            People

            • Assignee:
              rohithsharma Rohith Sharma K S
              Reporter:
              rohithsharma Rohith Sharma K S
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: