hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8327) distcpv2 and distcpv1 jars should not coexist
Date Mon, 07 May 2012 15:54:50 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robert Joseph Evans updated HADOOP-8327:

       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

Thanks Dave,

I have put this into trunk, branch-2, and branch-0.23
> distcpv2 and distcpv1 jars should not coexist
> ---------------------------------------------
>                 Key: HADOOP-8327
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8327
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.2
>            Reporter: Dave Thompson
>            Assignee: Dave Thompson
>             Fix For: 0.23.3, 2.0.0, 3.0.0
>         Attachments: HADOOP-8327-branch-0.23.2.patch, HADOOP-8327.patch, HADOOP-8327.patch
> Distcp v2 (hadoop-tools/hadoop-distcp/...)    and Distcp v1 (hadoop-tools/hadoop-extras/...)
are currently both built, and the resulting hadoop-distcp-x.jar and hadoop-extras-x.jar end
up in the same class path directory.   This causes some undeterministic problems, where v1
is launched when v2 is intended, or even v2 is launched, but may later fail on various nodes
because of mismatch with v1.
> According to
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html ("Understanding
class path wildcards")
> "The order in which the JAR files in a directory are enumerated in the expanded class
path is not specified and may vary from platform to platform and even from moment to moment
on the same machine."
> Suggest distcpv1 be deprecated at this point, possibly by discontinuing build of distcpv1.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message