AM is the master of an distributed application on YARN. It's supposed to negotiate with YARN for the cluster resources and monitor the status of the application. It's not associated with MapReduce. MapReduce V2 has its own AM, while Samza has one iteself as well.
On Tue, Apr 22, 2014 at 3:40 PM, Steve Yates <[email protected]>wrote: > Guys is it fair to say that YARN exposes an extension mechanism called the > ApplicationMaster and by default in yarn this master is a map-reduce > application master. > > In the case of samza we have implemented a streaming case of this AM which > takes full advantage of the parrallel / fault tolerant mechanisms built > into hadoop. > > So instead where we partition map reduce tasks bases on file size splits > in hdfs, we split a stream into stream tasks based on some filter key? Is > this correct. > > -S -- Zhijie Shen Hortonworks Inc. http://hortonworks.com/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
