Hama - + <title>Apache Hama - Getting Started with Hama

Return-Path: X-Original-To: apmail-hama-commits-archive@www.apache.org Delivered-To: apmail-hama-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C55C41749A for ; Tue, 30 Jun 2015 07:32:57 +0000 (UTC) Received: (qmail 17635 invoked by uid 500); 30 Jun 2015 07:32:57 -0000 Delivered-To: apmail-hama-commits-archive@hama.apache.org Received: (qmail 17584 invoked by uid 500); 30 Jun 2015 07:32:57 -0000 Mailing-List: contact commits-help@hama.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hama.apache.org Delivered-To: mailing list commits@hama.apache.org Received: (qmail 17440 invoked by uid 99); 30 Jun 2015 07:32:57 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2015 07:32:57 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id 63730AC08DD for ; Tue, 30 Jun 2015 07:32:57 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1688383 [3/6] - in /hama/site/trunk: ./ css/ fonts/ images/ js/ Date: Tue, 30 Jun 2015 07:32:56 -0000 To: commits@hama.apache.org From: edwardyoon@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150630073257.63730AC08DD@hades.apache.org> Added: hama/site/trunk/fonts/glyphicons-halflings-regular.svg URL: http://svn.apache.org/viewvc/hama/site/trunk/fonts/glyphicons-halflings-regular.svg?rev=1688383&view=auto ============================================================================== --- hama/site/trunk/fonts/glyphicons-halflings-regular.svg (added) +++ hama/site/trunk/fonts/glyphicons-halflings-regular.svg Tue Jun 30 07:32:56 2015 @@ -0,0 +1,229 @@ + + + \ No newline at end of file Added: hama/site/trunk/fonts/glyphicons-halflings-regular.ttf URL: http://svn.apache.org/viewvc/hama/site/trunk/fonts/glyphicons-halflings-regular.ttf?rev=1688383&view=auto ============================================================================== Binary file - no diff available. Propchange: hama/site/trunk/fonts/glyphicons-halflings-regular.ttf ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: hama/site/trunk/fonts/glyphicons-halflings-regular.woff URL: http://svn.apache.org/viewvc/hama/site/trunk/fonts/glyphicons-halflings-regular.woff?rev=1688383&view=auto ============================================================================== Binary file - no diff available. Propchange: hama/site/trunk/fonts/glyphicons-halflings-regular.woff ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Modified: hama/site/trunk/getting_started_with_hama.html URL: http://svn.apache.org/viewvc/hama/site/trunk/getting_started_with_hama.html?rev=1688383&r1=1688382&r2=1688383&view=diff ============================================================================== --- hama/site/trunk/getting_started_with_hama.html (original) +++ hama/site/trunk/getting_started_with_hama.html Tue Jun 30 07:32:56 2015 @@ -1,22 +1,22 @@ - + - Hama - + <title>Apache Hama - Getting Started with Hama - + - + @@ -28,7 +28,7 @@ ga('create', 'UA-46300992-1', 'apache.org'); ga('send', 'pageview'); - + @@ -105,23 +105,6 @@ - - - -

- External Links -
- Wiki -
- JIRA -
- Hama Twitter -
-

- + + + + + + + + +

+ +
+ +

+ + @@ -174,10 +142,13 @@ @@ -185,24 +156,10 @@ @@ -225,48 +182,93 @@ See the License for the specific language governing permissions and limitations under the License. --> -

Getting Started with Hama

-

This document describes how to install, configure and manage Hama clusters ranging from a few nodes to extremely large clusters with thousands of nodes.

+

+

Getting Started with Hama

+ +

This document describes how to install, configure and manage Hama clusters ranging from a few nodes to extremely large clusters with thousands of nodes.

-

Requirements

-

1. Make sure all required software is installed on all nodes in your cluster:

-

hadoop-1.0.x or higher version (non-secure version)
Sun Java JDK 1.6.x or higher version
SSH access to manage BSP deamons

+

Requirements

1. Make sure all required software is installed on all nodes in your cluster:

hadoop-1.0.x or higher version (non-secure version)
Sun Java JDK 1.7.x or higher version
SSH access to manage BSP deamons

2. Download Hama from the release page. + +

2. Download Hama from the release page.

For additional information consult our Compatibility Table

Mode

Just like Hadoop, we distinct between three modes:

Local Mode - This mode is the default mode if you download Hama (>= 0.3.0) and install it. When submitting a job it will run a local multithreaded BSP Engine on your server. It can be configured via the bsp.master.address property to local. You can adjust the number of threads used in this utility by setting the bsp.local.tasks.maximum property. See the Settings step how and where to configure this.
Pseudo Distributed Mode - This mode is when you just have a single server and want to launch all the deamon processes (BSPMaster, Groom and Zookeeper). It can be configured when you set the bsp.master.address to a host address e.g., localhost and put the same address into the groomservers file in the configuration directory. As stated it will run a BSPMaster, a Groom and a Zookeeper on your machine.
Distributed Mode - This mode is just like the "Pseudo Distributed Mode", but you have multiple machines, which are mapped in the groomservers file.

+

Mode

Just like Hadoop, we distinct between three modes:

Local Mode - This mode is the default mode if you download Hama (>= 0.3.0) and install it. When submitting a job it will run a local multithreaded BSP Engine on your server. It can be configured via the bsp.master.address property to local. You can adjust the number of threads used in this utility by setting the bsp.local.tasks.maximum property. See the Settings step how and where to configure this.
Pseudo Distributed Mode - This mode is when you just have a single server and want to launch all the deamon processes (BSPMaster, Groom and Zookeeper). It can be configured when you set the bsp.master.address to a host address e.g., localhost and put the same address into the groomservers file in the configuration directory. As stated it will run a BSPMaster, a Groom and a Zookeeper on your machine.
Distributed Mode - This mode is just like the "Pseudo Distributed Mode", but you have multiple machines, which are mapped in the groomservers file.

+ NOTE: We also support the Mesos and Yet Another Resource Negotiator (YARN), + so you're able to submit your BSP applications to the existing open source and enterprise clusters e.g., CDH, HDP, and Mesosphere without any installation. +

Configuration Files

The $HAMA_HOME/conf directory contains some configuration files for Hama. These are:

hama-env.sh - This file contains some environment variable settings used by Hama. You can use these to affect some aspects of Hama daemon behavior, such as where log files are stored, the maximum amount of heap used etc. The only variable you should need to change in this file is JAVA_HOME, which specifies the path to the Java 1.5.x installation used by Hama.
groomservers - This file lists the hosts, one per line, where the GroomServer daemons will run. By default this contains the single entry localhost
hama-default.xml - This file contains generic default settings for Hama daemons. Do not modify this file.
hama-site.xml - This file contains site specific settings for all Hama daemons and BSP jobs. This file is empty by default. Settings in this file override those in hama-default.xml. This file should contain settings that must be respected by all servers and clients in a Hama installation.

+

Configuration Files

The $HAMA_HOME/conf directory contains some configuration files for Hama. These are:

hama-env.sh - This file contains some environment variable settings used by Hama. You can use these to affect some aspects of Hama daemon behavior, such as where log files are stored, the maximum amount of heap used etc. The only variable you should need to change in this file is JAVA_HOME, which specifies the path to the Java 1.5.x installation used by Hama.
groomservers - This file lists the hosts, one per line, where the GroomServer daemons will run. By default this contains the single entry localhost
hama-default.xml - This file contains generic default settings for Hama daemons. Do not modify this file.
hama-site.xml - This file contains site specific settings for all Hama daemons and BSP jobs. This file is empty by default. Settings in this file override those in hama-default.xml. This file should contain settings that must be respected by all servers and clients in a Hama installation.

Startup Scripts

The $HAMA_HOME/bin directory contains some script used to start up the Hama daemons.

start-bspd.sh - Starts all Hama daemons, the BSPMaster, GroomServers and Zookeeper.

Note: You have to start Hama with the same user which is configured for Hadoop.

Setting up Hama

BSPMaster and Zookeeper settings - Figure out where to run your HDFS namenode and BSPMaster. Set the variable bsp.master.address to the BSPMaster's intended host:port. Set the variable fs.default.name to the HDFS Namenode's intended host:port.

Here's an example of a hama-site.xml file:

+

Startup Scripts

The $HAMA_HOME/bin directory contains some script used to start up the Hama daemons.

start-bspd.sh - Starts all Hama daemons, the BSPMaster, GroomServers and Zookeeper.

Note: You have to start Hama with the same user which is configured for Hadoop.

+

Setting up Hama

BSPMaster and Zookeeper settings - Figure out where to run your HDFS namenode and BSPMaster. Set the variable bsp.master.address to the BSPMaster's intended host:port. Set the variable fs.default.name to the HDFS Namenode's intended host:port.

Here's an example of a hama-site.xml file:

+
+
+   <?xml version="1.0"?>
   <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
   <configuration>
@@ -301,28 +303,42 @@
   </configuration>
 
 
+
 If you are managing your own ZooKeeper, you have to specify the port number as below:
 
-+
+
+   <property>
     <name>hama.zookeeper.property.clientPort</name>
     <value>2181</value>
   </property>
 
+
 See all Configuration Properties
     
-    Starting a Hama cluster
-    NOTE: Skip this step if you're in Local Mode.
+    
+

+Starting a Hama cluster
+    
+NOTE: Skip this step if you're in Local Mode.
     
Run the command:
     
-  +  
+
+   % $HAMA_HOME/bin/start-bspd.sh
-    This will startup a BSPMaster, GroomServers and Zookeeper on your machine.
-    Run the command:
-  +    
+This will startup a BSPMaster, GroomServers and Zookeeper on your machine.
+    
+Run the command:
+  
+
+   % $HAMA_HOME/bin/stop-bspd.sh
 
-    to stop all the daemons running on your cluster.
+    
+to stop all the daemons running on your cluster.
     
 
                   
@@ -332,18 +348,14 @@
 
     
             
-              Copyright ©                    2008-2014
-                        The Apache Software Foundation.
-            All Rights Reserved.      
-                    
-      
-
-                                                                  
-Apache Hama, Apache, the Apache feather logo, and
+                      
+                                                                          
+Apache Hama, Apache, the Apache feather logo, and
           the Apache Hama project logos are trademarks of The Apache Software
           Foundation. All other marks mentioned may be trademarks or registered
           trademarks of their respective owners.
-                  
+                          
+
                 
                           
         
@@ -352,5 +364,5 @@
         
                 

     

-  
+