You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2020/05/03 17:22:00 UTC
[jira] [Created] (YARN-10257) FS-CS converter: check deprecated
increment properties for mem/vcores and fix DRF check
Peter Bacsko created YARN-10257:
-----------------------------------
Summary: FS-CS converter: check deprecated increment properties for mem/vcores and fix DRF check
Key: YARN-10257
URL: https://issues.apache.org/jira/browse/YARN-10257
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Peter Bacsko
Assignee: Peter Bacsko
Two issues have been discovered during fs2cs testing:
1. The value of two properties are not checked:
{{yarn.scheduler.increment-allocation-mb}}
{{yarn.scheduler.increment-allocation-vcores}}
Although these two are marked as deprecated, they're still in use and must be handled.
2. The following piece of code is incorrect - the default scheduling policy can be different fromDRF, which is a problem is DRF is used everywhere:
{code}
private boolean isDrfUsed(FairScheduler fs) {
FSQueue rootQueue = fs.getQueueManager().getRootQueue();
AllocationConfiguration allocConf = fs.getAllocationConfiguration();
String defaultPolicy = allocConf.getDefaultSchedulingPolicy().getName();
if (DominantResourceFairnessPolicy.NAME.equals(defaultPolicy)) {
return true;
} else {
return isDrfUsedOnQueueLevel(rootQueue);
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org