You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2014/07/09 19:09:05 UTC

[jira] [Commented] (YARN-2266) Add an application timeout service in RM to kill applications which are not getting resources

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

Vinod Kumar Vavilapalli commented on YARN-2266:
-----------------------------------------------

bq. So after waiting for some time, if resources are not available, such applications can be made as failed.
What happens next? The apps are going to be resubmitted and they will still wait in the queue. Trying to understand the overall picture..

It seems like you want to reserve some capacity for a queue of periodically running applications to avoid that from happening in the first place..

> Add an application timeout service in RM to kill applications which are not getting resources
> ---------------------------------------------------------------------------------------------
>
>                 Key: YARN-2266
>                 URL: https://issues.apache.org/jira/browse/YARN-2266
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>            Reporter: Ashutosh Jindal
>
> Currently , If an application is submitted to RM, the app keeps waiting until the resources are allocated for AM. Such an application may be stuck till a resource is allocated for AM, and this may be due to over utilization of Queue or User limits etc. In a production cluster, some periodic running applications may have lesser cluster share. So after waiting for some time, if resources are not available, such applications can be made as failed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)