hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Navina Ramesh <nram...@linkedin.com.INVALID>
Subject Re: Ordering of ResourceRequest handling in the RM
Date Fri, 12 Jun 2015 01:58:53 GMT

From: Navina Ramesh <nramesh@linkedin.com<mailto:nramesh@linkedin.com>>
Date: Thursday, June 11, 2015 at 6:10 PM
To: "yarn-dev@hadoop.apache.org<mailto:yarn-dev@hadoop.apache.org>" <yarn-dev@hadoop.apache.org<mailto:yarn-dev@hadoop.apache.org>>
Cc: "kasha@cloudera.com<mailto:kasha@cloudera.com>" <kasha@cloudera.com<mailto:kasha@cloudera.com>>,
"vinodkv@apache.org<mailto:vinodkv@apache.org>" <vinodkv@apache.org<mailto:vinodkv@apache.org>>,
"Yi Pan (Data Infrastructure)" <yipan@linkedin.com<mailto:yipan@linkedin.com>>,
Chris Riccomini <criccomini@apache.org<mailto:criccomini@apache.org>>
Subject: Ordering of ResourceRequest handling in the RM

Hi yarn-devs,

I am trying to utilize YARN’s host-affinity feature in Apache Samza (SAMZA-617).

I have a question regarding the order in which the resource requests are executed by the RM.
Today, we make successive requests for x (say x = 3) containers for deploying a Samza job.
It looks like:
Request 1: (container-0, $hostX)
Request 2: (container-1, $hostY)
Request 3: (container-2, $hostZ)

When implementing the callback “onContainerAllocated” in the SamzaAppMaster, how can I
associate an allocated container with its corresponding containerRequest? Is there a way in
YARN to associate an allocated container to its request?

If not, is it correct to assume that the RM handles the requests in a FIFO manner and hence,
the order in which the onContainerAllocated callback is invoked will be the same as the request

This information will be very useful for Samza to implement host-affinity in its deployment
model. Please let me know.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message