[
https://issues.apache.org/jira/browse/YARN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461317#comment-13461317
]
Harsh J commented on YARN-56:
-----------------------------
+1 on Robert's timeout suggestion though (per app, with a reasonable default).
> Handle container requests that request more resources than available in the
> cluster
> -----------------------------------------------------------------------------------
>
> Key: YARN-56
> URL: https://issues.apache.org/jira/browse/YARN-56
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.0.2-alpha, 0.23.3
> Reporter: Hitesh Shah
>
> In heterogenous clusters, a simple check at the scheduler to check if the
> allocation request is within the max allocatable range is not enough.
> If there are large nodes in the cluster which are not available, there may be
> situations where some allocation requests will never be fulfilled. Need an
> approach to decide when to invalidate such requests. For application
> submissions, there will need to be a feedback loop for applications that
> could not be launched. For running AMs, AllocationResponse may need to
> augmented with information for invalidated/cancelled container requests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
