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

Posted to commits@samza.apache.org by "Bharath Kumarasubramanian (Jira)" <ji...@apache.org> on 2021/03/11 06:48:00 UTC

[jira] [Created] (SAMZA-2632) Processors should only write their own task locality to zookeeper

Bharath Kumarasubramanian created SAMZA-2632:
------------------------------------------------

             Summary: Processors should only write their own task locality to zookeeper
                 Key: SAMZA-2632
                 URL: https://issues.apache.org/jira/browse/SAMZA-2632
             Project: Samza
          Issue Type: Bug
            Reporter: Bharath Kumarasubramanian
            Assignee: Bharath Kumarasubramanian
             Fix For: 1.7


*Problem*:
 Processors update the task locality for all the tasks in the job model with their own locality regardless of whether the tasks belong to their container model or not.

*Description*: 
 As part of [SEP 11|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75957309], host affinity for standalone was introduced. For this feature, we persist the task locality in zookeeper so that subsequent rebalances take this locality into account when generating job model.

During job model consensus, we update the task locality for all the tasks and this results in incorrect locality depending on the order of writes.

*Solution*:
Only update the locality for the tasks that belong to the processor.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)