[
https://issues.apache.org/jira/browse/SAMZA-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Navina Ramesh updated SAMZA-1197:
---------------------------------
Fix Version/s: (was: 0.13.0)
0.14.0
> 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
> Fix For: 0.14.0
>
>
> 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)
