Hadoop is an Apache open source framework written in java that allows distributed processing of large datasets across clusters of computers using simple programming models.
The Hadoop framework application works in an environment that provides distributed storage and computation across clusters of computers. Hadoop is designed to scale up from single server to thousands of machines, each offering local computation and storage.
Pre Requirements
1) A machine with Ubuntu 14.04 LTS operating system installed.
2) Apache Hadoop 2.6.4 Software (Download Here)
Pseudo Distributed Mode (Single Node Cluster)
The Hadoop daemons run on a local machine, thus simulating a cluster on a small scale. Different Hadoop daemons run in different JVM instances, but on a single machine. HDFS is used instead of local FS.
Step 1 – Update. Open a terminal (CTRL + ALT + T) and type the following sudo command. It is advisable to run this before installing any package, and necessary to run it to install the latest updates, even if you have not added or removed any Software Sources.
|
1 |
$ sudo apt-get update |
Step 2 – Installing Java 7.
|
1 |
$ sudo apt-get install openjdk-<strong>7</strong>-jdk |
Step 3 – Install open-ssh server. It is a cryptographic network protocol for operating network services securely over an unsecured network. The best known example application is for remote login to computer systems by users.
|
1 |
$ sudo apt-get install openssh-server |
Step 4 – Create a Group. We will create a group, configure the group sudo permissions and then add the user to the group. Here ‘hadoop’ is a group name and ‘hduser’ is a user of the group.
|
1 |
$ sudo addgroup hadoop |
|
1 |
$ sudo adduser --ingroup hadoop hduser |
Step 5 – Configure the sudo permissions for ‘hduser’.
|
1 |
$ sudo visudo |
Since by default ubuntu text editor is nano we will need to use CTRL + O to edit.
|
1 |
ctrl+O |
Add the permissions to sudoers.
|
1 |
hduser ALL=(ALL) ALL |
Use CTRL + X keyboard shortcut to exit out. Enter Y to save the file.
|
1 |
ctrl+x |
Step 6 – Creating hadoop directory.
|
1 |
$ sudo mkdir /usr/local/hadoop |
Step 7 – Change the ownership and permissions of the directory /usr/local/hadoop. Here ‘hduser’ is an Ubuntu username.
|
1 |
$ sudo chown -R hduser /usr/local/hadoop |
|
1 |
$ sudo chmod -R <strong>755</strong> /usr/local/hadoop |
Step 8 – Switch User, is used by a computer user to execute commands with the privileges of another user account.
|
1 |
$ su hduser |
Step 9 – Change the directory to /home/hduser/Desktop , In my case the downloaded hadoop-2.6.4.tar.gz file is in /home/hduser/Desktop folder. For you it might be in /downloads folder check it.
|
1 |
$ cd /home/hduser/Desktop/ |
Step 10 – Untar the hadoop-2.6.4.tar.gz file.
|
1 |
$ tar xzf hadoop-<strong>2.6</strong>.<strong>4</strong>.<strong>tar</strong>.<strong>gz</strong> |
Step 11 – Move the contents of hadoop-2.6.4 folder to /usr/local/hadoop
|
1 |
$ mv hadoop-<strong>2.6</strong>.<strong>4</strong>/* /usr/local/hadoop |
Step 12 – Edit $HOME/.bashrc file by adding the java and hadoop path.
|
1 |
$ sudo gedit $HOME/.<strong>bashrc</strong> |
$HOME/.bashrc file. Add the following lines
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
# Set Hadoop-related environment variables export HADOOP_HOME=/usr/local/hadoop export HADOOP_MAPRED_HOME=$HADOOP_HOME export HADOOP_COMMON_HOME=$HADOOP_HOME export HADOOP_HDFS_HOME=$HADOOP_HOME export YARN_HOME=$HADOOP_HOME export HADOOP_COMMON_LIB_NATIVE_DIR=$HADOOP_HOME/lib/<strong>native</strong> PATH=$PATH:$HADOOP_HOME/sbin:$HADOOP_HOME/bin export HADOOP_INSTALL=$HADOOP_HOME export HADOOP_OPTS="$HADOOP_OPTS -Djava.library.path=/usr/local/hadoop/lib/native" # Set JAVA_HOME (we will also configure JAVA_HOME directly <strong>for</strong> Hadoop later on) export JAVA_HOME=/usr/lib/jvm/java-<strong>7</strong>-openjdk-amd64 |
Step 13 – Reload your changed $HOME/.bashrc settings
|
1 |
$ source $HOME/.<strong>bashrc</strong> |
Step 14 – Generating a new SSH public and private key pair on your local computer is the first step towards authenticating with a remote server without a password. Unless there is a good reason not to, you should always authenticate using SSH keys.
|
1 |
$ ssh-keygen -t rsa -P "" |
Step 15 – Now you can add the public key to the authorized_keys
|
1 |
$ cat $HOME/.<strong>ssh</strong>/id_rsa.<strong>pub</strong> >> $HOME/.<strong>ssh</strong>/authorized_keys |
Step 16 – Adding localhost to list of known hosts. A quick way of making sure that ‘localhost’ is added to the list of known hosts so that a script execution doesn’t get interrupted by a question about trusting localhost’s authenticity.
|
1 |
$ ssh localhost |
Step 17 – Change the directory to /usr/local/hadoop/etc/hadoop
|
1 |
$ cd $HADOOP_HOME/etc/hadoop |
Step 18 – Edit hadoop-env.sh file.
|
1 |
$ sudo gedit hadoop-env.<strong>sh</strong> |
Step 19 – Add the below lines to hadoop-env.sh file. Save and Close.
|
1 2 |
# remove comment and change java_HOME export JAVA_HOME=/usr/lib/jvm/java-<strong>7</strong>-openjdk-amd64 |
Step 20 – Edit core-site.xml file.
|
1 |
$ sudo gedit core-site.<strong>xml</strong> |
Step 21 – Add the below lines to core-site.xml file. Save and Close.
|
1 2 3 4 5 6 7 8 9 |
<property> <name>fs.<strong>default</strong>.<strong>name</strong></name> <value>hdfs:<em>//localhost:9000</value></em> <description>The name of the <strong>default</strong> file system. A URI whose scheme and authority determine the FileSystem implementation. The uri's scheme determines the config property (fs.<strong>SCHEME</strong>.<strong>impl</strong>) naming the FileSystem implementation class. The uri's authority is used to determine the host, port, etc. <strong>for</strong> a filesystem.</description> </property> |
Step 22 – Edit hdfs-site.xml file.
|
1 |
$ sudo gedit hdfs-site.<strong>xml</strong> |
Step 23 – Add the below lines to hdfs-site.xml file. Save and Close.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
<property> <name>dfs.<strong>replication</strong></name> <value><strong>1</strong></value> </property> <property> <name>dfs.<strong>name</strong>.<strong>dir</strong></name> <value>/app/hadoop/tmp/namenode</value> </property> <property> <name>dfs.<strong>data</strong>.<strong>dir</strong></name> <value>/app/hadoop/tmp/datanode</value> </property> |
Step 24 – Edit yarn-site.xml file.
|
1 |
$ sudo gedit yarn-site.<strong>xml</strong> |
Step 25 – Add the below lines to yarn-site.xml file. Save and Close.
|
1 2 3 4 |
<property> <name>yarn.<strong>nodemanager</strong>.<strong>aux</strong>-services</name> <value>mapreduce_shuffle</value> </property> |
Step 26 – Copy the default mapred-site.xml.template to mapred-site.xml
|
1 |
$ cp mapred-site.<strong>xml</strong>.<strong>template</strong> mapred-site.<strong>xml</strong> |
Step 27 – Edit mapred-site.xml file.
|
1 |
$ sudo gedit mapred-site.<strong>xml</strong> |
Step 28 – Add the below lines to mapred-site.xml file. Save and Close.
|
1 2 3 4 |
<property> <name>mapreduce.<strong>framework</strong>.<strong>name</strong></name> <value>yarn</value> </property> |
Step 29 – Edit slaves file.
|
1 |
$ sudo gedit slaves |
Step 30 – Add the below line to slaves file. Save and Close.
|
1 |
localhost |
Step 31 – Creating /app/hadoop/tmp directory.
|
1 |
$ sudo mkdir /app/hadoop/tmp |
Step 32 – Change the ownership and permissions of the directory /app/hadoop/tmp. Here ‘hduser’ is an Ubuntu username.
|
1 |
$ sudo chown -R hduser /app/hadoop/tmp |
|
1 |
$ sudo chmod -R <strong>755</strong> /app/hadoop/tmp |
Step 33 – Change the directory to /usr/local/hadoop/sbin
|
1 |
$ cd /usr/local/hadoop/sbin |
Step 34 – Format the datanode.
|
1 |
$ hadoop namenode -format |
Step 35 – Start NameNode daemon and DataNode daemon.
|
1 |
$ start-dfs.<strong>sh</strong> |
Step 36 – Start yarn daemons.
|
1 |
$ start-yarn.<strong>sh</strong> |
OR
Instead of steps 35 and 36 you can use below command. It is deprecated now.
|
1 |
$ start-all.<strong>sh</strong> |
Step 37 – The JPS (Java Virtual Machine Process Status Tool) tool is limited to reporting information on JVMs for which it has the access permissions.
|
1 |
$ jps |
Once the Hadoop cluster is up and running check the web-ui of the components as described below
NameNode Browse the web interface for the NameNode; by default it is available at
|
1 |
http:<em>//localhost:50070/</em> |
ResourceManager Browse the web interface for the ResourceManager; by default it is available at
|
1 |
http:<em>//localhost:8088/</em> |
Step 38 – Make the HDFS directories required to execute MapReduce jobs.
|
1 |
$ bin/hdfs dfs -mkdir /user |
|
1 |
$ bin/hdfs dfs -mkdir /user/hduser |
Step 39 – Copy the input files into the distributed filesystem.
|
1 |
$ hdfs dfs -put /usr/local/hadoop/etc/hadoop /user/hduser/input |
Step 40 – Run some of the examples provided.
|
1 |
$ hadoop jar /usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-<strong>2.6</strong>.<strong>4</strong>.<strong>jar</strong> grep /user/hduser/input /user/hduser/output 'dfs[a-z.]+' |
Step 41 – Examine the output files.
|
1 |
$ hdfs dfs -cat /user/hduser/output/* |
Step 42 – Stop NameNode daemon and DataNode daemon.
|
1 |
$ stop-dfs.<strong>sh</strong> |
Step 43 – Stop Yarn daemons.
|
1 |
$ stop-yarn.<strong>sh</strong> |
OR
Instead of steps 42 and 43 you can use below command. It is deprecated now.
|
1 |
$ stop-all.<strong>sh</strong> |