[
https://issues.apache.org/jira/browse/SAMZA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984681#comment-13984681
]
Chris Riccomini commented on SAMZA-124:
---------------------------------------
Here is the discussion on the YARN mailing lists:
https://www.mail-archive.com/[email protected]/msg06936.html
bq. yarn.scheduler.capacity.node-locality-delay
Sounds like we need to try capacity with
yarn.scheduler.capacity.node-locality-delay set to 40, or something.
> Provide AM based antiaffinity to avoid clumping of containers
> -------------------------------------------------------------
>
> Key: SAMZA-124
> URL: https://issues.apache.org/jira/browse/SAMZA-124
> Project: Samza
> Issue Type: Improvement
> Components: container
> Affects Versions: 0.6.0
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Fix For: 0.7.0
>
>
> We're seeing YARN scheduling lots of containers on the same box causing NIC
> saturation and cluster degradation. Pending SAMZA-74 (and its dependency,
> YARN-1042), it would be good to have some basic anti-affinity support at the
> AM level. We can be selective about what nodes we request and accept from
> the RM, hopefully spreading the containers around the cluster more evenly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
