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 "Íñigo Goiri (JIRA)" <ji...@apache.org> on 2019/05/29 18:43:00 UTC
[jira] [Commented] (YARN-2489) ResouceOption's overcommitTimeout
should be respected during resource update on NM
[ https://issues.apache.org/jira/browse/YARN-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851197#comment-16851197 ]
Íñigo Goiri commented on YARN-2489:
-----------------------------------
I think this is solved by YARN-999 now.
Closing this one as duplicate.
> ResouceOption's overcommitTimeout should be respected during resource update on NM
> ----------------------------------------------------------------------------------
>
> Key: YARN-2489
> URL: https://issues.apache.org/jira/browse/YARN-2489
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: graceful, nodemanager, scheduler
> Reporter: Junping Du
> Priority: Major
>
> The ResourceOption to update NM's resource has two properties: Resource and OvercommitTimeout. The later property is used to guarantee resource is withdrawn after timeout is hit if resource is reduced to a value and current resource consumption exceeds the new value. It currently use default value -1 which means no timeout, and we should make this property work when updating NM resource.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org