Database Reference
In-Depth Information
or
/etc/profile.d/hadoop.sh
. On most systems,
/etc/profile
automatically includes all scripts in
/etc/profile.d
. If YARN was
unpacked into the
/usr/local
directory, the
/etc/profile.d/
hadoop.sh
file would look like this:
export YARN_HOME=/usr/local/hadoop
export HADOOP_MAPRED_HOME=$YARN_HOME
export HADOOP_COMMON_HOME=$YARN_HOME
export HADOOP_HDFS_HOME=$YARN_HOME
export PATH=${PATH}:${YARN_HOME}/bin:${YARN_HOME}/sbin
To see these changes reflected in the environment, log out and log back in
again or open a new terminal. After doing that, checking the
YARN_HOME
environmentvariableshouldgive
/usr/local/hadoop
,andacheckofthe
Hadoop version should return 2.2.0:
$ echo $YARN_HOME
/usr/local/hadoop
$ hadoop version
Hadoop 2.2.0
Subversion https://svn.apache.org/repos/asf/hadoop/
common -r 1529768
Compiled by hortonmu on 2013-10-07T06:28Z
Compiled with protoc 2.5.0
From source with checksum
79e53ce7994d1628b240f09af91e1af4
This command was run using
/usr/local/hadoop-2.2.0/share/hadoop/common/
hadoop-common-2.2.0.jar
Because this grid is being used for Samza, it is not necessary to configure
HDFS. If the grid is also going to be used for Map-Reduce workloads,
refer to the appropriate YARN documentation for the configuration of the
NameNode
and
DataNode
servers. The only thing that needs to be
configured for Samza is the
yarn-site.xml
file found in
/usr/local/
hadoop/etc/hadoop
(replacing
resource-manager.mydomain.net
with an appropriate hostname):
