[YARN-11133] YarnClient gets the wrong EffectiveMinCapacity value

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.3, 3.3.2
• Fix Version/s: 3.4.0, 3.2.4, 3.3.5
• Component/s: api
• Labels: pull-request-available
• Assignee: Zilong Zhu
• Reporter: Zilong Zhu
• Created: 07/May/22 15:05
• Updated: 17/May/22 18:14
• Resolved: 16/May/22 16:41

Description

It calls the QueueConfigurations#getEffectiveMinCapacity to get the wrong value when I use the YarnClient. I found some bugs with QueueConfigurationsPBImpl#mergeLocalToBuilder.

private void mergeLocalToBuilder() {
  if (this.effMinResource != null) {
    builder
        .setEffectiveMinCapacity(convertToProtoFormat(this.effMinResource));
  }
  if (this.effMaxResource != null) {
    builder
        .setEffectiveMaxCapacity(convertToProtoFormat(this.effMaxResource));
  }
  if (this.configuredMinResource != null) {
    builder.setEffectiveMinCapacity(
        convertToProtoFormat(this.configuredMinResource));
  }
  if (this.configuredMaxResource != null) {
    builder.setEffectiveMaxCapacity(
        convertToProtoFormat(this.configuredMaxResource));
  }
} 

configuredMinResource was incorrectly assigned to effMinResource. This causes the real effMinResource to be overwritten and configuredMinResource is null. 

Issue Links

• is caused by: YARN-7254 UI and metrics changes related to absolute resource configuration
• links to: GitHub Pull Request #4280