[
https://issues.apache.org/jira/browse/KAFKA-10843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251960#comment-17251960
]
Matthias J. Sax commented on KAFKA-10843:
-----------------------------------------
{quote}You want me to update the Kafka-streams version to 2.6.0?
{quote}
I might be worth a try.
{quote}With regards to using allMetadata(), this wont still give me the
particular store where my key is right? It would give all the hosts where the
store is present, but my key could be on any of them.
{quote}
Well, yes, but you see the partition information, and thus you could hash the
key yourself to find the right instance.
Curious to hear your answer to Bruno's questions. – If you use custom
partitioning, you would need to hand in a custom `StreamsPartitioner` to allow
KafkaStreams to compute the right partitions to find the right instance.
> 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)
