You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/05/05 22:41:15 UTC

[jira] [Commented] (SAMZA-124) Provide AM based antiaffinity to avoid clumping of containers

    [ https://issues.apache.org/jira/browse/SAMZA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989941#comment-13989941 ] 

Chris Riccomini commented on SAMZA-124:
---------------------------------------

OK, node locality set to 40 with capacity scheduler *still* puts all 32 containers on only 4 out of 14 nodes. The rest remain empty. It seems that specifically asking for hosts with capacity and node locality set to 40 is still ignored.

> 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: Chris Riccomini
>             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)