szilard-nemeth commented on a change in pull request #3279:
URL: https://github.com/apache/hadoop/pull/3279#discussion_r694822828
##########
File path:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md
##########
@@ -744,6 +744,14 @@ Changing queue/scheduler properties and adding/removing
queues can be done in tw
Remove the queue configurations from the file and run refresh as described
above
+### Enabling periodic configuration refresh
+Enabling queue configuration periodic refresh allows changing the
configuration by editing the *conf/capacity-scheduler.xml* without the
necessicity of calling yarn rmadmin -refreshQueues.
+
+| Property | Description |
+|:---- |:---- |
+| `yarn.resourcemanager.scheduler.monitor.enable` | Enabling monitoring is
necessary for the periodic refresh. Default value is false. |
+| `yarn.resourcemanager.scheduler.monitor.policies` | You should add
`org.apache.hadoop.yarn.server.resourcemanager.capacity.QueueConfigurationAutoRefreshPolicy`
to the policies list. Default value is
`org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.ProportionalCapacityPreemptionPolicy`.
|
Review comment:
Also, please also describe that this is a configuration property that
holds a list of classes. So actually, it can be not too useful to remove the
ProportionalCapacityPreemptionPolicy as it would turn off the preemption
feature, so it should be explained in a nutshell that by adding more classes
means more monitor tasks will be launched. Please make this a bit more
disambiguous.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
