[
https://issues.apache.org/jira/browse/SAMZA-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741741#comment-14741741
]
Yan Fang commented on SAMZA-619:
--------------------------------
{quote}
Then, however, we will end up 2 patterns of allocation. Some of the code will
be duplicated. We need to maintain parity as and when we make changes to the
old way of doing things. It just felt maintaining 2 different patterns was
going to be a lot of work.
{quote}
Yes, I agreed on this part. If we have 2 patterns of allocation, it is better
that they share the same code.
My question mainly is in the assigning container side. Can we use something
like
{code}
// Resource Request
ResourceRequest rsrcRequest = Records.newRecord(ResourceRequest.class);
// setup requirements for hosts
// whether a particular rack/host is needed
// useful for applications that are sensitive
// to data locality
rsrcRequest.setHostName("*");
{code}
to assign the containers to a particular host? Does this way have some
drawbacks?
> Modify Samza AppMaster to enable host-affinity
> ----------------------------------------------
>
> Key: SAMZA-619
> URL: https://issues.apache.org/jira/browse/SAMZA-619
> Project: Samza
> Issue Type: Task
> Components: yarn
> Affects Versions: 0.10.0
> Reporter: Navina Ramesh
> Assignee: Navina Ramesh
> Fix For: 0.10.0
>
> Attachments: SAMZA-619-0.patch, SAMZA-619-1.patch
>
>
> In order to enable host-affinity in YARN, the Samza App Master must include
> the node list in the resource request.
> The node list can be obtained from the Job Coordinator that provides the
> container-to-host mapping (SAMZA-618)
> YARN must also be configured to use FairScheduler with continuous scheduling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
