[YARN-4164] Retrospect update ApplicationPriority API return type

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: resourcemanager
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed
• Assignee: Rohith Sharma K S
• Reporter: Rohith Sharma K S
• Created: 16/Sep/15 05:35
• Updated: 06/Jan/17 08:16
• Resolved: 18/Dec/15 22:27

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.