[
https://issues.apache.org/jira/browse/KAFKA-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452031#comment-15452031
]
ASF GitHub Bot commented on KAFKA-4104:
---------------------------------------
GitHub user dguy opened a pull request:
https://github.com/apache/kafka/pull/1804
KAFKA-4104: Queryable state metadata is sometimes invalid
If the thread or process is not the coordinator the Cluster instance in
StreamPartitionAssignor will always be null. This builds an instance of the
Cluster with the metadata associated with the Assignment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dguy/kafka kafka-4104
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1804.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1804
----
commit 6cc1149d22ef85d6b0c5ace3d7e624f4f66fefa6
Author: Damian Guy <damian....@gmail.com>
Date: 2016-08-31T11:51:16Z
build Cluster in StreamPartitionAssignor.onAssignment
----
> Queryable state metadata is sometimes invalid
> ---------------------------------------------
>
> Key: KAFKA-4104
> URL: https://issues.apache.org/jira/browse/KAFKA-4104
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Eno Thereska
> Assignee: Damian Guy
> Fix For: 0.10.1.0
>
>
> The streams.metadataForKey method sometimes fails because the cluster-wide
> metadata is invalid/null in non-leader nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
