[ 
https://issues.apache.org/jira/browse/YARN-8394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510671#comment-16510671
 ] 

Hudson commented on YARN-8394:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14417 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/14417/])
YARN-8394. Improve data locality documentation for Capacity Scheduler. (wwei: 
rev 29024a62038c297f11e8992601f2522ffffc7da7)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/CapacityScheduler.md
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/conf/capacity-scheduler.xml


> Improve data locality documentation for Capacity Scheduler
> ----------------------------------------------------------
>
>                 Key: YARN-8394
>                 URL: https://issues.apache.org/jira/browse/YARN-8394
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>            Priority: Major
>             Fix For: 3.2.0, 3.1.1, 3.0.4
>
>         Attachments: YARN-8394.001.patch, YARN-8394.002.patch
>
>
> YARN-6344 introduces a new parameter 
> {{yarn.scheduler.capacity.rack-locality-additional-delay}} in 
> capacity-scheduler.xml, we need to add some documentation in 
> {{CapacityScheduler.md}} accordingly.
> Moreover, we are seeing more and more clusters are separating storage and 
> computation where file system is always remote, in such cases we need to 
> introduce how to compromise data locality in CS otherwise MR jobs are 
> suffering.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to