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

Posted to commits@samza.apache.org by "Daniel Nishimura (Jira)" <ji...@apache.org> on 2019/10/03 17:37:00 UTC

[jira] [Updated] (SAMZA-2334) ProxyGrouper selection based on Host Affinity not whether job is stateful

     [ https://issues.apache.org/jira/browse/SAMZA-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Nishimura updated SAMZA-2334:
------------------------------------
    Description: Changes in partition count of input Kafka topic that is not a multiple of previous topic, causes the grouper to not start up. We should check if the job is a stateful one instead of only checking if the job has host-affinity enabled. Also need to add a configuration to disable the proxy grouper in case the Kafka topic cannot be the multiple of the previous topic and to unblock the job from running.  (was: Changes in partition count of input Kafka topic that is not a multiple of previous topic, causes the grouper to not start up. We should check if the job is a stateful one instead)

> ProxyGrouper selection based on Host Affinity not whether job is stateful
> -------------------------------------------------------------------------
>
>                 Key: SAMZA-2334
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2334
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Daniel Nishimura
>            Assignee: Daniel Nishimura
>            Priority: Major
>
> Changes in partition count of input Kafka topic that is not a multiple of previous topic, causes the grouper to not start up. We should check if the job is a stateful one instead of only checking if the job has host-affinity enabled. Also need to add a configuration to disable the proxy grouper in case the Kafka topic cannot be the multiple of the previous topic and to unblock the job from running.



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