You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Levani Kokhreidze (Jira)" <ji...@apache.org> on 2020/11/05 18:24:00 UTC

[jira] [Assigned] (KAFKA-10686) Pluggable standby tasks assignor for Kafka Streams

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

Levani Kokhreidze reassigned KAFKA-10686:
-----------------------------------------

    Assignee: Levani Kokhreidze

> Pluggable standby tasks assignor for Kafka Streams
> --------------------------------------------------
>
>                 Key: KAFKA-10686
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10686
>             Project: Kafka
>          Issue Type: New Feature
>          Components: streams
>            Reporter: Levani Kokhreidze
>            Assignee: Levani Kokhreidze
>            Priority: Major
>              Labels: needs-kip
>
> In production, Kafka Streams instances often run across different clusters and availability zones. In order to guarantee high availability of the Kafka Streams deployments, users would need more granular control over which instances standby tasks can be created. 
> Idea of this ticket is to expose interface for Kafka Streams which can be implemented by the users to control where standby tasks can be created.
> Kafka Streams can have RackAware assignment as a default implementation that will take into account `rack.id` of the application and make sure that standby tasks are created on different racks. 
> Point of this ticket though is to give more flexibility to users on standby task creation, in cases where just rack awareness is not enough. 



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