Sunil Govindan commented on YARN-7494:

Thanks [~cheersyang].

bq.my opinion is if this causes burden ending up with changing a lot of files, 
it seems better to limit this feature in CS. Just let the sorting manager be a 
common service would be enough.

With current approach, we can actually have a cleaner implementation generic. 
Though it touches few files, it is not much causing problem. Also we can avoid 
few instance of check which I think is always better to have a cleaner impl. 

Other issue are addressed and uploaded a new patch. Pls help to review

> 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 Govindan
>            Assignee: Sunil Govindan
>            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.006.patch, YARN-7494.007.patch, YARN-7494.008.patch, 
> YARN-7494.009.patch, YARN-7494.010.patch, YARN-7494.11.patch, 
> YARN-7494.12.patch, YARN-7494.13.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