[
https://issues.apache.org/jira/browse/YARN-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Muhammad Samir Khan updated YARN-6867:
--------------------------------------
Attachment: YARN-6867.001.patch
Added a new unit test in TestRM to demonstrate how an app submission can fail
with a InvalidResourceRequestException being thrown. Changes to
AbstractYarnScheduler to report the correct value after the wait time is over.
Also added a unit test to TestAbstractYarnScheduler.
This does not handle all the corner cases, e.g. the RM reported the max values
before the wait time was over but the app was submitted after the wait time had
expired. But this should handle the more reproducible one.
> 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
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
