Differences between revisions 2 and 3
Revision 2 as of 2014-07-02 06:13:40
Size: 3362
Editor: 129
Revision 3 as of 2014-07-02 06:14:49
Size: 3353
Editor: 129
Deletions are marked like this. Additions are marked like this.
Line 37: Line 37:
Additionally, there are several other properties that will need to be considered when setting up hama for the first time: There are also several other properties that will need to be considered when setting up hama for the first time:

Getting Started with Hama on Mesos


In order to run Hama on Mesos it is required that Mesos already be installed on the cluster. Instructions to set up Mesos may be found at the project website: http://mesos.apache.org/.


Be sure to build Hama with your version of Mesos specified:

mvn clean install -Phadoop1 -Dhadoop.version=1.x.x -Dmesos.version=0.18.2

The groom servers will be set up by Mesos during execution of a job. In order for Mesos to do this, you will need to upload a built version of Hama to a place where the Mesos slaves can find it, such as the HDFS:

hadoop fs -put hama-7.0.0.tar.gz /hama-7.0.0.tar.gz


There are several Mesos related properties that must be set in hama-site.xml:


Recommended Value




Instructs the scheduler to use Mesos to execute tasks of each job



This is the URI of the Hama distribution. Upload this yourself.



This is an override for the total maximum tasks that may be run. The default behavior is to determine a value based on the available groom servers. However, if using Mesos, the groom servers are not yet allocated. So, a value indicating the maximum number of slots available in the cluster is needed.


This is the address of the Mesos master instance. If you're using Zookeeper for master election, use the Zookeeper address here (i.e.,zk://zk.apache.org:2181/hadoop/mesos).



Java opts for the groom server child processes.

Hama requires one cpu and memory defined by bsp.child.java.opts for each slot. This means that a cluster with bsp.tasks.maximum.total set to 2 and bsp.child.jova.opts set to -Xmx1024m will need at least 2 cpus and and 2048m of memory.

Manually distributing the configuration is not necessary. Hama and Mesos will distribute the configuration and provide overrides where necessary.

There are also several other properties that will need to be considered when setting up hama for the first time:


Default Value




Temporary directory on the local filesystem.


Comma separated list of servers in the Zookeeper Quorum



The port to which the zookeeper clients connect

Starting The BSPMaster

With Hama on Mesos you only need to set up and start the BSPMaster. After setting the configuration the bsp master may be started:

% $HAMA_HOME/bin/hama-daemon.sh start bspmaster


In order to test the setup, run an example from Hama:

$HAMA_HOME/bin/hama jar hama-examples-x.x.x.jar gen fastgen 100 10 randomgraph 2

Then verify that Mesos tasks are being created run. Do this by navigating to the Mesos status page and clicking on the id of the Hama framework. There should be tasks listed in either the active or completed tasks section.

Please email any questions to user@hama.apache.org

GettingStartedMesos (last edited 2015-05-18 03:31:01 by edwardyoon)