hama-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hama Wiki] Trivial Update of "Architecture" by Edward J. Yoon
Date Fri, 04 Jun 2010 07:19:01 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hama Wiki" for change notification.

The "Architecture" page has been changed by Edward J. Yoon.
The comment on this change is: Add explain for programming interface design..
http://wiki.apache.org/hama/Architecture?action=diff&rev1=122&rev2=123

--------------------------------------------------

  
   * TODO: (shortly) explain what is the BSP? and Hama BSP?
  
- One BSP cluster consists of one BSPMaster, multiple GroomServer and one or more zookeeper
servers in a network environment.
+ One BSP cluster consists of one BSPMaster, multiple !GroomServer and one or more zookeeper
servers in a network environment.
  
   * work in progress [[https://issues.apache.org/jira/browse/HAMA-251|HAMA-251]],[[https://issues.apache.org/jira/browse/HAMA-258|HAMA-258]]
  ==== BSPMaster ====
@@ -39, +39 @@

   6. Controlling fault. 
   7. Providing users with the cluster control interface.
  
- A BSP Master and multiple grooms are started by the script. Then, the bsp master starts
up with a RPC server for groom servers. Groom servers starts up with a BSPPeer instance -
later, BSPPeer needs to be integrated with GroomServer - and a RPC proxy to contact the bsp
master. After started, each groom periodically sends a heartbeat message that encloses its
groom server status, including maximum task capacity, unused memory, and so on. 
+ A BSP Master and multiple grooms are started by the script. Then, the bsp master starts
up with a RPC server for groom servers. Groom servers starts up with a BSPPeer instance -
later, BSPPeer needs to be integrated with !GroomServer - and a RPC proxy to contact the bsp
master. After started, each groom periodically sends a heartbeat message that encloses its
groom server status, including maximum task capacity, unused memory, and so on. 
  
  Each time the bsp master receives a heartbeat message, it brings up-to-date groom server
status - the bsp master makes use of groom servers' status in order to effectively assign
tasks to idle groom servers - and returns a heartbeat response that contains assigned tasks
and others actions that a groom server has to do. For now, we have a FIFO job scheduler and
very simple task assignment algorithms.
  ==== GroomServer ====
@@ -50, +50 @@

  
  ==== BSP Programming Interface ====
  
+ Hama BSP programming interface is designed to be similar to the !MapReduce interface. This
allows the framework to be less complex than the traditional BSP libraries capable of executing
sequential code, and we has been able to provide the user-friendly and intuitive programming
interface to existing users of !MapReduce framework. See the below example code:
- Hama BSP programming interface is designed to be similar to the MapReduce interface.
- 
- This allows a less complex than an traditional BSP libraries capable of executing sequential
code, and we has been able to provide the user-friendly and intuitive programming interface
to existing users of MapReduce framework.
  
  {{{
  public class BSPEaxmple {

Mime
View raw message