hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MENG DING (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-4671) There is no need to acquire CS lock when completing a container
Date Thu, 04 Feb 2016 16:11:39 GMT
MENG DING created YARN-4671:
-------------------------------

             Summary: There is no need to acquire CS lock when completing a container
                 Key: YARN-4671
                 URL: https://issues.apache.org/jira/browse/YARN-4671
             Project: Hadoop YARN
          Issue Type: Improvement
            Reporter: MENG DING
            Assignee: MENG DING


In YARN-4519, we discovered that there is no need to acquire CS lock in CS#completedContainerInternal,
because:

* Access to critical section are already guaranteed by queue lock.
* It is not essential to guard {{schedulerHealth}} with cs lock. All maps in schedulerHealth
are concurrent maps.

With this fix, we can truly claim that CS#allocate doesn't require CS lock.



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

Mime
View raw message