[
https://issues.apache.org/jira/browse/YARN-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419342#comment-16419342
]
Sunil G commented on YARN-7494:
-------------------------------
[~cheersyang] Thanks for the update. I also discussed with [~leftnoteasy] and
feel the former approach is better. So we ll use like below
{code:java}
<property>
<name>yarn.scheduler.capacity.multi-node-sorting.polices</name>
<value>resource-usage</value>
</property>
<property>
<name>yarn.scheduler.capacity.multi-node-sorting.policy.resource-usage.class</name>
<value>org.apache.hadoop.yarn.server.resourcemanager.scheduler.placement.ResourceUsageSortingNodesPolicy</value>
</property>
<property>
<name>yarn.scheduler.capacity.multi-node-sorting.policy.resource-usage.sorting-task.interval.ms</name>
<value>3000</value>
</property>{code}
> Add muti node lookup support for better placement
> -------------------------------------------------
>
> Key: YARN-7494
> URL: https://issues.apache.org/jira/browse/YARN-7494
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Reporter: Sunil G
> Assignee: Sunil G
> Priority: Major
> Attachments: YARN-7494.001.patch, YARN-7494.002.patch,
> YARN-7494.003.patch, YARN-7494.004.patch, YARN-7494.005.patch,
> YARN-7494.v0.patch, YARN-7494.v1.patch, multi-node-designProposal.png
>
>
> Instead of single node, for effectiveness we can consider a multi node lookup
> based on partition to start with.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
