[
https://issues.apache.org/jira/browse/HADOOP-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950263#comment-14950263
]
Steve Loughran commented on HADOOP-11127:
-----------------------------------------
bq. I agree that #3 might be technically possible but, as you say, it requires
wholesale changes to the Hadoop distro build and release process and I'm simply
not in a position to be able to do that.
Well, there are enough people in this discussion that we can start thinking
about this, especially if we involve colleagues and the bigtop team. Proposal
#2 is making enough changes to the system that it's going to impact it.
We'll get automatic cleanup on YARN of extracted code, as long as it is done in
the path given to each launched container.
> Improve versioning and compatibility support in native library for downstream
> hadoop-common users.
> --------------------------------------------------------------------------------------------------
>
> Key: HADOOP-11127
> URL: https://issues.apache.org/jira/browse/HADOOP-11127
> Project: Hadoop Common
> Issue Type: Bug
> Components: native
> Reporter: Chris Nauroth
> Assignee: Alan Burlison
> Attachments: HADOOP-11064.003.patch, proposal.txt
>
>
> There is no compatibility policy enforced on the JNI function signatures
> implemented in the native library. This library typically is deployed to all
> nodes in a cluster, built from a specific source code version. However,
> downstream applications that want to run in that cluster might choose to
> bundle a hadoop-common jar at a different version. Since there is no
> compatibility policy, this can cause link errors at runtime when the native
> function signatures expected by hadoop-common.jar do not exist in
> libhadoop.so/hadoop.dll.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
