[
https://issues.apache.org/jira/browse/HADOOP-10953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316355#comment-14316355
]
Hudson commented on HADOOP-10953:
---------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #2052 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2052/])
HADOOP-10953. NetworkTopology#add calls NetworkTopology#toString without
holding the netlock (Liang Xie via Colin P. McCabe) (cmccabe: rev
6338ce3ae8870548cac5abe2f685748b5efb13c1)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/NetworkTopology.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> NetworkTopology#add calls NetworkTopology#toString without holding the netlock
> ------------------------------------------------------------------------------
>
> Key: HADOOP-10953
> URL: https://issues.apache.org/jira/browse/HADOOP-10953
> Project: Hadoop Common
> Issue Type: Bug
> Components: net
> Affects Versions: 3.0.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Priority: Minor
> Fix For: 2.7.0
>
> Attachments: HADOOP-10953.txt
>
>
> Found this issue while reading the related code. In
> NetworkTopology.toString() method, there is no thread safety guarantee
> directly, it's called by add/remove, and inside add/remove, most of
> this.toString() calls are protected by rwlock, except a couple of error
> handling codes, one possible fix is that moving them into lock as well, due
> to not heavy operations, so no obvious downgration should be observed per my
> current knowledge.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
