On Thu, May 19, 2011 at 1:39 PM, Eli Collins <[EMAIL PROTECTED]> wrote:
> Thanks for contributing. Supporting ARM on Hadoop will require a
> number of different changes right? Eg given that Hadoop currently
> depends on some Sun-specific classes, and requires a Sun-compatible
> JVM you'll have to work around this dependency somehow, there's not a
> Sun JVM for ARM right?
Actually, there is a Sun JVM for ARM, and it works quite well:
Currently, it's just a JRE, so you have to use another JDK for javac,
etc., but I'm optimistic that we'll see a Sun Java SE JDK for ARM
servers one of these days, given all the ARM server activity from
Marvell, and nVidia
With the patches I submitted, Hadoop builds completely and nearly all
of the Commons and HDFS unit tests pass with OpenJDK on ARM. (Some of
the Map/Reduce unit tests have some crashes due to a bug in the
OpenJDK build I'm using.) I need to re-run the unit tests with the Sun
JRE and see if they pass; other tests/benchmarks have run much faster
and more reliably with the Sun JRE, so I anticipate better results.
I've run tests like TestDFSIO with the Sun JRE and have had no
> If there's a handful of additional changes then let's make an umbrella
> jira for Hadoop ARM support and make the issues you've already filed
> sub-tasks. You can ping me off-line on how to that if you want.
> Supporting non-x86 processors and non-gcc compilers is an additional
> maintenance burden on the project so it would be helpful to have an
> end-game figured out so these patches don't bitrot in the meantime.
I really don't anticipate any additional changes at this point. No
Java or C++ code changes have been necessary; it's simply removing
-m32 from CFLAGS/LDFLAGS and adding ARM to the list of processors in
apsupport.m4 (which contains lots of other unsupported processors
anyway). And just to be clear, pretty much everyone uses gcc for
compilation on ARM, so supporting another compiler is unnecessary for
I certainly don't want to increase maintenance burden at this point,
especially given that data center-grade ARM servers are still in the
prototype stage. OTOH, these changes seem pretty trivial to me, and
allow other developers (particularly those evaluating ARM and those
involved in the Ubuntu ARM Server 11.10 release this fall:
get Hadoop up and running without having to patch the build.
I'll follow up offline though, so I can better understand any concerns
you may still have.
> On Tue, May 10, 2011 at 5:13 PM, Trevor Robinson <[EMAIL PROTECTED]> wrote:
>> Is the native build failing on ARM (where gcc doesn't support -m32) a
>> known issue, and is there a workaround or fix pending?
>> $ ant -Dcompile.native=true
>> [exec] make all-am
>> [exec] make: Entering directory
>> [exec] /bin/bash ./libtool --tag=CC --mode=compile gcc
>> -DHAVE_CONFIG_H -I. -I/home/trobinson/dev/hadoop-common/src/native
>> -Isrc/org/apache/hadoop/security -Isrc/org/apache/hadoop/io/nativeio/
>> -g -Wall -fPIC -O2 -m32 -g -O2 -MT ZlibCompressor.lo -MD -MP -MF
>> .deps/ZlibCompressor.Tpo -c -o ZlibCompressor.lo `test -f
>> 'src/org/apache/hadoop/io/compress/zlib/ZlibCompressor.c' || echo
>> [exec] libtool: compile: gcc -DHAVE_CONFIG_H -I.