[
https://issues.apache.org/jira/browse/SAMZA-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741127#comment-14741127
]
Navina Ramesh commented on SAMZA-619:
-------------------------------------
We could have it like what we do today for non-host-affinity. 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.
If you think otherwise, I am ok bringing back the old code as well. Do you
think it will be better to keep the main thread approach for non-host-affinity
yarn?
> 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)
