hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10147) Upgrade to commons-logging 1.1.3 to avoid potential deadlock in MiniDFSCluster
Date Sat, 07 Dec 2013 09:23:35 GMT

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

Steve Loughran commented on HADOOP-10147:
-----------------------------------------

I'd be happy with the upgrade under the big  HADOOP-9991 pom upgrade banner: if you do the
update and run the full hadoop test suite *and whatever is breaking your code* I'll put the
patch in to branch-2+

> 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
>            Priority: Minor
>
> 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#6144)

Mime
View raw message