You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Muhammad Samir Khan (JIRA)" <ji...@apache.org> on 2017/07/25 15:19:00 UTC
[jira] [Created] (YARN-6867) AbstractYarnScheduler reports the
configured maximum resources, instead of the actual, even after the
configured waittime
Muhammad Samir Khan created YARN-6867:
-----------------------------------------
Summary: 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
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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org