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=167&rev2=168 [[BSPMaster|BSPMaster]] is responsible for the following: - * maintaining its own [[BSPMaster|state]]. + * Maintaining its own [[BSPMaster|state]]. * Maintaining groom server status. * Maintaining supersteps and other counters in a cluster. * Maintaining [[JobInformation|job progress information]]. @@ -32, +32 @@ === GroomServer === - A [[GroomServer|Groom Server]] (shortly referred to as groom) is a process that manages life cycle of bsp tasks assigned by BSPMaster. Each groom contacts the BSPMaster, and reports task statuses 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 for data-locality. However, in a massive parallel environment, the benefit of data locality is lost when large amount of virtual processes must be multiplexed onto physical processes[2]. + A [[GroomServer|Groom Server]] (shortly referred to as groom) is a process that manages life cycle of bsp tasks assigned by BSPMaster. Each groom contacts the BSPMaster, and reports task statuses 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 run on one physical node to get the best performance for data-locality. Note that in a massive parallel environment, the benefit of data locality is lost when large amount of virtual processes must be multiplexed onto physical processes[2]. === Zookeeper ===
