[
https://issues.apache.org/jira/browse/YARN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718675#comment-13718675
]
Omkar Vinit Joshi commented on YARN-56:
---------------------------------------
I agree timeout behavior will be useful but we should somehow tell the AM that
request either expired or was rejected in allocate response and not expect AM
to ask again after time has elapsed. i.e. Indirectly telling AM not to ask
again until previous request is rejected and is notified back to AM thereby
avoiding unnecessary requests from AM...I think YARN-394 is tracking this
similar issue..
> Handle container requests that request more resources than currently
> available in the cluster
> ---------------------------------------------------------------------------------------------
>
> Key: YARN-56
> URL: https://issues.apache.org/jira/browse/YARN-56
> Project: Hadoop YARN
> Issue Type: Improvement
> 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
