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] Update of "Architecture" by ChiaHungLin
Date Sun, 18 Aug 2013 07:10:45 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 ChiaHungLin:
https://wiki.apache.org/hama/Architecture?action=diff&rev1=158&rev2=159

   * Distributing execution classes and configuration across groom servers.
   * Providing users with the cluster control interface (web and console based).
  
- 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 to which groom servers can dynamically register itself. 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.
  

Mime
View raw message