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

Konstantinos Karanasos commented on YARN-5468:
----------------------------------------------

Thanks for the comment, [~cheersyang]. Yes, I have read YARN-4902.
It is definitely related, but in this JIRA we are focusing in particular on the 
scheduling of long running jobs/services.
In that sense, YARN-4902 is more general. On the other hand, unlike YARN-4902, 
we will be providing the option of service planning, that is, we will be able 
to look at multiple services at once and plan their execution in a more 
holistic manner than the scheduler can do (given that the scheduler looks at 
one resource request at a time). This can be seen as related to the planning 
phase of YARN-1051.

> Scheduling of long-running applications
> ---------------------------------------
>
>                 Key: YARN-5468
>                 URL: https://issues.apache.org/jira/browse/YARN-5468
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: capacityscheduler, fairscheduler
>            Reporter: Konstantinos Karanasos
>            Assignee: Konstantinos Karanasos
>         Attachments: YARN-5468.prototype.patch
>
>
> This JIRA is about the scheduling of applications with long-running tasks.
> It will include adding support to the YARN for a richer set of scheduling 
> constraints (such as affinity, anti-affinity, cardinality and time 
> constraints), and extending the schedulers to take them into account during 
> placement of containers to nodes.
> We plan to have both an online version that will accommodate such requests as 
> they arrive, as well as a Long-running Application Planner that will make 
> more global decisions by considering multiple applications at once.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to