YARN-10860. Make max container per heartbeat configs refreshable. Contributed by Eric Badger.

This commit is contained in:
zhuqi-lucas 2021-07-21 15:31:44 +08:00
parent e634bf33f3
commit 0441efe1fc
2 changed files with 11 additions and 2 deletions

View File

@ -393,7 +393,10 @@ void initScheduler(Configuration configuration) throws
+ getMaximumResourceCapability() + ", " + "asynchronousScheduling="
+ scheduleAsynchronously + ", " + "asyncScheduleInterval="
+ asyncScheduleInterval + "ms" + ",multiNodePlacementEnabled="
+ multiNodePlacementEnabled);
+ multiNodePlacementEnabled + ", " + "assignMultipleEnabled="
+ assignMultipleEnabled + ", " + "maxAssignPerHeartbeat="
+ maxAssignPerHeartbeat + ", " + "offswitchPerHeartbeatLimit="
+ offswitchPerHeartbeatLimit);
} finally {
writeLock.unlock();
}
@ -485,8 +488,14 @@ public void reinitialize(Configuration newConf, RMContext rmContext,
this.isLazyPreemptionEnabled = this.conf.getLazyPreemptionEnabled();
// Setup how many containers we can allocate for each round
assignMultipleEnabled = this.conf.getAssignMultipleEnabled();
maxAssignPerHeartbeat = this.conf.getMaxAssignPerHeartbeat();
offswitchPerHeartbeatLimit = this.conf.getOffSwitchPerHeartbeatLimit();
LOG.info("assignMultipleEnabled = " + assignMultipleEnabled + "\n" +
"maxAssignPerHeartbeat = " + maxAssignPerHeartbeat + "\n" +
"offswitchPerHeartbeatLimit = " + offswitchPerHeartbeatLimit);
super.reinitialize(newConf, rmContext);
}
maxRunningEnforcer.updateRunnabilityOnReload();

View File

@ -702,7 +702,7 @@ Note, this feature should be disabled if YARN is deployed separately with the fi
* Container Allocation per NodeManager Heartbeat
The `CapacityScheduler` supports the following parameters to control how many containers can be allocated in each NodeManager heartbeat.
The `CapacityScheduler` supports the following parameters to control how many containers can be allocated in each NodeManager heartbeat. These parameters are refreshable via *yarn rmadmin -refreshQueues*.
| Property | Description |
|:---- |:---- |