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

Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2017/04/07 21:45:42 UTC

[jira] [Created] (SAMZA-1197) Locality should be used in standalone execution (host-affinity)

Navina Ramesh created SAMZA-1197:
------------------------------------

             Summary: Locality should be used in standalone execution (host-affinity)
                 Key: SAMZA-1197
                 URL: https://issues.apache.org/jira/browse/SAMZA-1197
             Project: Samza
          Issue Type: Sub-task
            Reporter: Navina Ramesh
            Assignee: Navina Ramesh


With SAMZA-1084 and SEP-1, we started using a varying list of processorId (String), instead of a monotonically increasing bounded set for integers as containerId. This is essential to leverage data-locality for processing, aka host-affinity feature. 
Some of the changes related to making this work:
1. Use localitymanager in JobModel Manager
2.GroupByContainerCount (which is the default TaskNameGrouper) assumes the bounded integer of containerId for rebalancing tasks. This should be changes to work with a varying set of processorId Strings.





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)