Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@kafka.apache.org
Date: Sat, 23 Sep 2017 04:28:14 +0000 (UTC)
From: "Guozhang Wang (JIRA)" <jira@apache.org>
To: jira@kafka.apache.org
Message-ID: <JIRA.13037652.1485342526000.182669.1506140894165@Atlassian.JIRA>
In-Reply-To: <JIRA.13037652.1485342526000@Atlassian.JIRA>
References: <JIRA.13037652.1485342526000@Atlassian.JIRA> <JIRA.13037652.1485342526266@jira-lw-us.apache.org>
Subject: [jira] [Updated] (KAFKA-4696) Streams standby task assignment
 should be state-store aware
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 23 Sep 2017 04:28:25 -0000


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

Guozhang Wang updated KAFKA-4696:
---------------------------------
    Fix Version/s:     (was: 1.0.0)
                   1.1.0

> Streams standby task assignment should be state-store aware
> -----------------------------------------------------------
>
>                 Key: KAFKA-4696
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4696
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.2.0, 0.11.0.0
>            Reporter: Damian Guy
>             Fix For: 1.1.0
>
>
> Task Assignment is currently not aware of which tasks have State Stores. This can result in uneven balance of standby task assignment as all tasks are assigned, but only those tasks with state-stores are ever created by {{StreamThread}}. So what seems like an optimal strategy during assignment time could be sub-optimal post-assignment.
> For example, lets say we have 4 tasks (2 with state-stores), 2 clients, numStandbyReplicas = 1. Each client would get 2 active and 2 standby tasks.  One of the clients may end up with both state-store tasks, while the other has none.
> Further to this, standby task configuration is currently "all or nothing". It might make sense to allow more fine grained configuration, i.e., the ability to specify the number of standby replicas individually for each stateful operator.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)