[YARN-7219] Make AllocateRequestProto compatible with branch-2/branch-2.8

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 3.0.0
• Component/s: yarn
• Target Version/s: 3.0.0
• Hadoop Flags: Reviewed
• Release Note: Change update_requests field id to 7. This matches the current field id in branch-2 and branch-2.8.
• Assignee: Ray Chiang
• Reporter: Ray Chiang
• Created: 19/Sep/17 20:53
• Updated: 25/Oct/19 20:26
• Resolved: 03/Oct/17 22:15

Description

For yarn_service_protos.proto, we have the following code in
(branch-2.8.0, branch-2.8, branch-2)

message AllocateRequestProto {
  repeated ResourceRequestProto ask = 1;
  repeated ContainerIdProto release = 2;
  optional ResourceBlacklistRequestProto blacklist_request = 3;
  optional int32 response_id = 4;
  optional float progress = 5;
  repeated ContainerResourceIncreaseRequestProto increase_request = 6;
  repeated UpdateContainerRequestProto update_requests = 7;
}

For yarn_service_protos.proto, we have the following code in
(trunk)

message AllocateRequestProto {
  repeated ResourceRequestProto ask = 1;
  repeated ContainerIdProto release = 2;
  optional ResourceBlacklistRequestProto blacklist_request = 3;
  optional int32 response_id = 4;
  optional float progress = 5;
  repeated UpdateContainerRequestProto update_requests = 6;
}

Notes

• YARN-3866 was the original JIRA for container resizing.
• YARN-5221 is what introduced the incompatible change.
• In branch-2/branch-2.8/branch-2.8.0, this protobuf change was undone by "Addendum patch to YARN-3866: fix incompatible API change."
• There was a similar API fix done in YARN-6071.

Issue Links

• is related to: YARN-3866 AM-RM protocol changes to support container resizing
• is related to: YARN-5221 Expose UpdateResourceRequest API to allow AM to request for change in container properties
• is related to: YARN-6071 Fix incompatible API change on AM-RM protocol due to YARN-3866 (trunk only)