converted to 1.6 markup
|Deletions are marked like this.||Additions are marked like this.|
|Line 3:||Line 3:|
|Hadoop Clusters can be created on Virtual Machines. This works, but performance (especially to virtualized disks) can be significantly slower than for physical machines.||Hadoop Clusters can be created on Virtual Machines. See [[Virtual Hadoop]] for the benefits and challenges present in such deployment.|
Hadoop Clusters can be created on Virtual Machines. See Virtual Hadoop for the benefits and challenges present in such deployment.
Process to set up a cluster using the Hadoop shell scripts
- All machines should be brought up to date, with the same version of Java, Hadoop, etc.
- All machine's(both VM's and physical machines) public key are distributed to all "~/.ssh/authorized_keys" file.
- conf/hadoop-site.xml file is similar for all the machines.
- /etc/hosts file must contain all the machines(VM,Physical machine) IP and Hostname.
- The local hostname entry in /etc/hosts must not point to 127.0.0.1 or any other loopback address (some laptop-friendly Linux distributions do this). It should be to the assigned IP address.
- conf/slaves must contain the hostname of all slaves including VM's and physical machine.
- conf/masters must contain only master's hostname.
- both conf/masters and conf/slaves files must be similar in all the participating machines.
- The hadoop home directory should be same for all the machines like "/root/hadoop-0.18.2/"
- Finally execute the Namenode -format command only in the Master machine.
Most of this configuration can be done on a single machine image, the problematic area is host naming. Virtual networks with reverseDNS allow the hostname to be picked up from the network. If you use this,
- The namenode and job tracker hostnames should remain constant; these need separate images.
- Bring up other machines afterwards; use an empty conf/slaves file.
Here are things that can cause trouble.
- Multiple virtual network adapters. It is simpler with one network adapter/node
- Machines changing hostname/IPAddress on a reboot. For a long-lived virtual cluster you need stable machine names.
- Machines whose hostname doesn't match the hostname the network assigns it. It thinks it is "granton", the network thinks it is "dhcp-169-45", that being the name everything else talks to it by.
- Machines that think they have the same hostname. You get this if you clone VMs and don't rename them.
- Pauses of an entire VM for 5-10s or longer. This happens when the virtual host is overloaded and your VM has been swapped out. Host less VMs, or have them ask for less memory.
- Wierd clock drift where it can even run backwards. Again, don't overload your machines.
- All redundant virtual servers (e.g. Namenode and secondary NN) being hosted on the same physical machine. At that point, you don't have redundancy or failover any more.