Sunil G commented on YARN-7494:

This was a bit due. Sorry for the delay.

Updated as per comments. However instead of a CompositeService, we can use the 
model like SchedulerMonitor. Its more easy and also will help to avoid creating 
custom sorters without extending AbstractService. Pls check.

> 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.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

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to