You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2016/05/23 21:30:12 UTC
[jira] [Updated] (YARN-4979) FSAppAttempt demand calculation
considers demands at multiple locality levels different
[ https://issues.apache.org/jira/browse/YARN-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthik Kambatla updated YARN-4979:
-----------------------------------
Summary: FSAppAttempt demand calculation considers demands at multiple locality levels different (was: FSAppAttempt adds duplicate ResourceRequest to demand in updateDemand.)
> FSAppAttempt demand calculation considers demands at multiple locality levels different
> ---------------------------------------------------------------------------------------
>
> Key: YARN-4979
> URL: https://issues.apache.org/jira/browse/YARN-4979
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Affects Versions: 2.8.0, 2.7.2
> Reporter: zhihai xu
> Assignee: zhihai xu
> Attachments: YARN-4979.001.patch
>
>
> FSAppAttempt adds duplicate ResourceRequest to demand in updateDemand. We should only count ResourceRequest for ResourceRequest.ANY when calculate demand.
> Because {{hasContainerForNode}} will return false if no container request for ResourceRequest.ANY and both {{allocateNodeLocal}} and {{allocateRackLocal}} will also decrease the number of containers for ResourceRequest.ANY.
> This issue may cause current memory demand overflow(integer) because duplicate requests can be on multiple nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org