[
https://issues.apache.org/jira/browse/KAFKA-10843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249967#comment-17249967
]
Matthias J. Sax commented on KAFKA-10843:
-----------------------------------------
I don't think that a stretch cluster deployment should make a difference. –
Also not sure if there would be another 2.5 bug-fix release. But I would
suspect it's a client side issue. Can you update your Kafka Streams library to
see if the issue persists?
As a workaround, I guess you can just `allMetadata()` and filter based on
`HostInfo`?
> Kafka Streams metadataForKey method returns null but allMetadata has the
> details
> --------------------------------------------------------------------------------
>
> Key: KAFKA-10843
> URL: https://issues.apache.org/jira/browse/KAFKA-10843
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.5.1
> Reporter: Maria Thomas
> Priority: Major
>
> Our application runs on multiple instances and to enable us to use get the
> key information from the state store we use "metadataForKey" method to
> retrieve the StreamMetadata and using the hostname do an RPC call to the host
> to get the value associated with the key.
> This call was working fine in our DEV and TEST environments, however, it is
> failing one our production clusters from the start. On further debugging, I
> noticed the allMetadata() method was returning the state stores with the host
> details as expected. However, it would not be feasible to go through each
> store explicitly to get the key details.
> To note, the cluster I am using is a stretch cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
