[
https://issues.apache.org/jira/browse/HADOOP-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861432#comment-13861432
]
Hudson commented on HADOOP-10147:
---------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #441 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/441/])
HADOOP-10147 HDFS-5678 Upgrade to commons-logging 1.1.3 to avoid potential
deadlock in MiniDFSCluster (stevel:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1554803)
* /hadoop/common/trunk
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-project/pom.xml
> Upgrade to commons-logging 1.1.3 to avoid potential deadlock in MiniDFSCluster
> ------------------------------------------------------------------------------
>
> Key: HADOOP-10147
> URL: https://issues.apache.org/jira/browse/HADOOP-10147
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 2.2.0
> Reporter: Eric Sirianni
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 2.4.0
>
> Attachments: HADOOP-10147-001.patch
>
>
> There is a deadlock in commons-logging 1.1.1 (see LOGGING-119) that can
> manifest itself while running {{MiniDFSCluster}} JUnit tests.
> This deadlock has been fixed in commons-logging 1.1.2. The latest version
> available is commons-logging 1.1.3, and Hadoop should upgrade to that in
> order to address this deadlock.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
