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 thomasjungblut: http://wiki.apache.org/hama/Architecture?action=diff&rev1=155&rev2=156 <<TableOfContents(5)>> + == General == + - Hama consists of three major components: BSPMaster, GroomServers and Zookeeper. It is very similar with Hadoop architecture, only except the portion of communication and synchronization mechanisms. + Apache Hama consists of three major components: BSPMaster, GroomServers and Zookeeper. It is very similar with Hadoop architecture, only except the portion of communication and synchronization mechanisms. + + In a normal usecase the user submits a so called "Job" which is a definition of how to run a computation. + A job once submitted will have multiple tasks that are launched across the cluster. === BSPMaster === BSPMaster is responsible for the following: * Maintaining groom server status. - * Controlling super steps in a cluster. + * Maintaining supersteps and other counters in a cluster. * Maintaining job progress information. - * Scheduling Jobs and Assigning tasks to groom servers + * Scheduling Jobs and assigning tasks to groom servers - * Disseminating execution class across groom servers. + * Distributing execution classes and configuration across groom servers. - * Controlling fault. - * Providing users with the cluster control interface. + * 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. @@ -22, +26 @@ === GroomServer === - A Groom Server (shortly referred to as groom) is a process that performs bsp tasks assigned by BSPMaster. Each groom contacts the BSPMaster, and it takes assigned tasks and reports its status by means of periodical piggybacks with BSPMaster. Each groom is designed to run with HDFS or other distributed storages. Basically, a groom server and a data node should be run on one physical node. + A Groom Server (shortly referred to as groom) is a process that launches bsp tasks assigned by BSPMaster. Each groom contacts the BSPMaster, and it takes assigned tasks and reports its status by means of periodical piggybacks with BSPMaster. Each groom is designed to run with HDFS or other distributed storages. Basically, a groom server and a data node should be run on one physical node to get the best performance. (Data-locality) === Zookeeper === - A Zookeeper is used to manage the efficient barrier synchronisation of the BSPPeers. Later, it will also be used for the area of a fault tolerance system. + A Zookeeper is used to manage the efficient barrier synchronization of the BSPPeers. Later, it will also be used for the area of a fault tolerance system.
