hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brook Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition
Date Mon, 22 Feb 2016 16:33:18 GMT

    [ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157240#comment-15157240
] 

Brook Zhou commented on YARN-4677:
----------------------------------

Hi [~djp], I currently have no plan, would appreciate if you could work on it. Thanks.

> RMNodeResourceUpdateEvent update from scheduler can lead to race condition
> --------------------------------------------------------------------------
>
>                 Key: YARN-4677
>                 URL: https://issues.apache.org/jira/browse/YARN-4677
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: graceful, resourcemanager, scheduler
>    Affects Versions: 2.7.1
>            Reporter: Brook Zhou
>
> When a node is in decommissioning state, there is time window between completedContainer()
and RMNodeResourceUpdateEvent get handled in scheduler.nodeUpdate (YARN-3223). 
> So if a scheduling effort happens within this window, the new container could still get
allocated on this node. Even worse case is if scheduling effort happen after RMNodeResourceUpdateEvent
sent out but before it is propagated to SchedulerNode - then the total resource is lower than
used resource and available resource is a negative value. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message