[
https://issues.apache.org/jira/browse/HADOOP-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125735#comment-14125735
]
Todd Lipcon commented on HADOOP-11064:
--------------------------------------
[~ste...@apache.org] -- hmm, I'm not 100% following here. Are you suggesting
that we are supposed to support mixed-version installations? I'd always assumed
that, if someone is running hadoop 2.4 client, then they would _only_ have
hadoop 2.4 artifacts on their path (classpath and java.library.path alike).
Here you're saying that the user has Hadoop 2.4 jars with Hadoop 2.6 SOs on the
same classpath.
In the same way that we don't expect HDFS 2.6 to work with a Common 2.4 JAR, I
don't think this is a supported scenario. Is this scenario listed in any of our
compatibility documentation?
> UnsatisifedLinkError with hadoop 2.4 JARs on hadoop-2.6 due NativeCRC32
> method changes
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-11064
> URL: https://issues.apache.org/jira/browse/HADOOP-11064
> Project: Hadoop Common
> Issue Type: Bug
> Components: native
> Affects Versions: 2.6.0
> Environment: Hadoop 2.6 cluster, trying to run code containing hadoop
> 2.4 JARs
> Reporter: Steve Loughran
> Priority: Blocker
>
> The private native method names and signatures in {{NativeCrc32}} were
> changed in HDFS-6561 ... as a result hadoop-common-2.4 JARs get unsatisifed
> link errors when they try to perform checksums.
> This essentially stops Hadoop 2.4 applications running on Hadoop 2.6 unless
> rebuilt and repackaged with the hadoop- 2.6 JARs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
