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-11064) UnsatisifedLinkError with hadoop 2.4 JARs on hadoop-2.6 due NativeCRC32 method changes
Date Wed, 10 Sep 2014 08:08:29 GMT

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

Steve Loughran commented on HADOOP-11064:
-----------------------------------------

# I have nothing against versioning, but IMO that can be a different JIRA, "add versioning
to the libhadoop". This JIRA is covering linkage errors which we can fix.
# w.r.t patch 3, the log of exceptions should include the stack trace, perhaps.

bq. There are a few months until 2.6 will be released-- do we really need to hack this? 

Yes. Because those of us who have switched our code to only work against branch-2 are the
one finding bugs sooner rather than later. If we weren't, this issue wouldn't have surfaced
until hadoop-2.6 shipped —at which point the fixes become an even bigger piece of firefighting
in a sprint to get 2.6.1 out the door the following week.

If branch-2 isn't in a state usable by anyone downstream, it doesn't get used, regressions
don't get picked up.

Right now, for us, it isn't usable —because we're the only team that's tried to deploy HBase
0.98 on a Hadoop 2.6 codebase cluster. 

Furthermore, I don't think it is "a hack", it is "retain the entry points which hadoop 2.4
code expect of the native library"

> 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
>            Assignee: Colin Patrick McCabe
>            Priority: Blocker
>         Attachments: HADOOP-11064.001.patch, HADOOP-11064.002.patch, HADOOP-11064.003.patch
>
>
> 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)

Mime
View raw message