[
https://issues.apache.org/jira/browse/KAFKA-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6796.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
> Surprising UNKNOWN_TOPIC error for produce/fetch requests to non-replicas
> -------------------------------------------------------------------------
>
> Key: KAFKA-6796
> URL: https://issues.apache.org/jira/browse/KAFKA-6796
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 1.1.0, 1.0.1
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
> Fix For: 1.2.0
>
>
> Currently if the client sends a produce request or a fetch request to a
> broker which isn't a replica, we return UNKNOWN_TOPIC_OR_PARTITION. This is a
> bit surprising to see when the topic actually exists. It would be better to
> return NOT_LEADER to avoid confusion. Clients typically handle both errors by
> refreshing metadata and retrying, so changing this should not cause any
> change in behavior on the client. This case can be hit following a partition
> reassignment after the leader is moved and the local replica is deleted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
