kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3890) Kafka Streams: task assignment is not maintained on cluster restart or rolling restart
Date Wed, 29 Jun 2016 22:21:15 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355908#comment-15355908
] 

ASF GitHub Bot commented on KAFKA-3890:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/1543


> Kafka Streams: task assignment is not maintained on cluster restart or rolling restart
> --------------------------------------------------------------------------------------
>
>                 Key: KAFKA-3890
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3890
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Henry Cai
>            Assignee: Henry Cai
>              Labels: api, newbie
>
> Currently the task assignment in TaskAssignor is not deterministic.  During cluster restart
or rolling restart, even though the participating worker nodes are the same, but the TaskAssignor
is not able to maintain a deterministic mapping, so about 20% partitions will be reassigned
which would cause state repopulation on cluster restart time.
> When the participating worker nodes are not changed, we really just want to keep the
old task assignment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message