[
https://issues.apache.org/jira/browse/YARN-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100276#comment-16100276
]
Muhammad Samir Khan commented on YARN-6867:
-------------------------------------------
Sorry, it looks like the problem was solved in trunk via YARN-4719. I should
have checked on trunk before proceeding. Closing the JIRA now.
> AbstractYarnScheduler reports the configured maximum resources, instead of
> the actual, even after the configured waittime
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-6867
> URL: https://issues.apache.org/jira/browse/YARN-6867
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Reporter: Muhammad Samir Khan
> Assignee: Nathan Roberts
> Attachments: YARN-6867.001.patch
>
>
> AbstractYarnScheduler has a configured wait time during which it reports the
> maximum resources from the configuration instead of the actual resources
> available in the cluster. However, the first query after the wait time
> expiration is responded by the configured maximum resources instead of the
> actual maximum resources. This can result in a app submission to fail with an
> InvalidResourceRequestException (will attach a unit test in the patch) since
> the maximum resources reported by the RM is different than the one it sanity
> checks against at app submission.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
