[jira] [Commented] (YARN-9958) Remove the invalid lock in ContainerExecutor

2019-12-03 Thread Hudson (Jira)


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

Hudson commented on YARN-9958:
--

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17718 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17718/])
YARN-9958. Remove the invalid lock in ContainerExecutor (#1704) (aajisaka: rev 
c48de9aa2ddf7622648c4410612ffc035861df63)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/ContainerExecutor.java


> Remove the invalid lock in ContainerExecutor
> 
>
> Key: YARN-9958
> URL: https://issues.apache.org/jira/browse/YARN-9958
> Project: Hadoop YARN
>  Issue Type: Improvement
>Reporter: Wanqiang Ji
>Assignee: Wanqiang Ji
>Priority: Major
> Fix For: 3.3.0
>
>
> ContainerExecutor has ReadLock and WriteLock. These used to call get/put 
> method of ConcurrentMap. Due to the ConcurrentMap providing thread safety and 
> atomicity guarantees, so we can remove the lock.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org



[jira] [Commented] (YARN-9958) Remove the invalid lock in ContainerExecutor

2019-11-14 Thread Tao Yang (Jira)


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

Tao Yang commented on YARN-9958:


Thanks [~jiwq] for this improvement. Patch LGTM, the related r/w lock only work 
for ContainerExecutor#pidFiles which is a concurrent hash map and no need to be 
guaranteed by additional lock.
 I will commit this a few days later if no further comments.

> Remove the invalid lock in ContainerExecutor
> 
>
> Key: YARN-9958
> URL: https://issues.apache.org/jira/browse/YARN-9958
> Project: Hadoop YARN
>  Issue Type: Improvement
>Reporter: Wanqiang Ji
>Assignee: Wanqiang Ji
>Priority: Major
>
> ContainerExecutor has ReadLock and WriteLock. These used to call get/put 
> method of ConcurrentMap. Due to the ConcurrentMap providing thread safety and 
> atomicity guarantees, so we can remove the lock.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org