CDH Client Configuration Environment Variables in Oracle Big Data Appliance v4.0.0
(Doc ID 1965898.1)
Last updated on JANUARY 30, 2015
Applies to:Big Data Appliance Integrated Software - Version 4.0 and later
On Oracle Big Data Appliance (BDA)/Exadata CDH Client Integration, the documentation tells us to reconfigure hadoop-env.sh (unsecured cluster) like this:
ln -s $HADOOP_HOME/../../../bin-mapreduce1 $HADOOP_HOME/bin
ln -s $HADOOP_HOME/../../../etc/hadoop-mapreduce1 $HADOOP_HOME/conf
rm -f $HADOOP_HOME/lib/slf4j-log4j*jar
Why are the alias and symlink commands there? Also, as this file is run before every hadoop command, it will start spawning "already exists" errors after its first run.
Additionally, all references to the HADOOP_HOME concern the "mapreduce1" subdirectory. Isn't this where the MRv1 things are? Is this normal (exdata will use MRv1) or is this a mixup?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document