hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7596) Enable jsvc to work with Hadoop RPM package
Date Wed, 31 Aug 2011 00:59:10 GMT

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

Eric Yang commented on HADOOP-7596:

Jakob, yes, but there is only one release tar ball which contains both i386 and x86_64 libraries.
 There is no unique location for jsvc which bundled in Hadoop.  Hence, the release tarball
is effectively 32 bit jsvc only.

Ideally, there should be one tarball/rpm/deb per architecture build.  However, having separated
tar ball per architecture build prevents us from having a single signed hadoop-core*.jar file
to be push to maven repository.

Therefore, to solve this problem, we probably should retain the single tar ball release, but
bundle both jsvc in the release tar ball.  The only change would be the shell script to do
the late binding to select the right jsvc to use at runtime.

RPM/DEB packages should only package jsvc base on the building architecture.

Does this sound reasonable?

> Enable jsvc to work with Hadoop RPM package
> -------------------------------------------
>                 Key: HADOOP-7596
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7596
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions:
>         Environment: Java 6, RedHat EL 5.6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For:
> For secure Hadoop 0.20.2xx cluster, datanode can only run with 32 bit jvm because Hadoop
only packages 32 bit jsvc.  The build process should download proper jsvc versions base on
the build architecture.  In addition, the shell script should be enhanced to locate hadoop
jar files in the proper location.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message