[MAPREDUCE-7151] RMContainerAllocator#handleJobPriorityChange expects application_priority always

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.2, 3.3.0, 3.2.1
• Assignee: Bilwa S T
• Reporter: Bibin Chundatt
• Created: 15/Oct/18 10:05
• Updated: 24/Oct/18 18:59
• Resolved: 24/Oct/18 18:15

Description

As per yarn_service.proto AllocateResponseProto application_priority is optional field.
But RMContainerAllocator#handleJobPriorityChange expects to have application priority always in response which is not mandatory.

  private void handleJobPriorityChange(AllocateResponse response) {
    Priority priorityFromResponse = Priority.newInstance(response
        .getApplicationPriority().getPriority());

    // Update the job priority to Job directly.
    getJob().setJobPriority(priorityFromResponse);
  }

message AllocateResponseProto {
..
  optional hadoop.common.TokenProto am_rm_token = 12;
  optional PriorityProto application_priority = 13;
  optional CollectorInfoProto collector_info = 14;
..
}

Issue Links

• is related to: MAPREDUCE-6515 Update Application priority in AM side from AM-RM heartbeat