[
https://issues.apache.org/jira/browse/KAFKA-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-6546.
-----------------------------------
Resolution: Fixed
Reviewer: Ismael Juma
Fix Version/s: (was: 2.1.0)
2.0.0
> Add ENDPOINT_NOT_FOUND_ON_LEADER error code for missing listener
> ----------------------------------------------------------------
>
> Key: KAFKA-6546
> URL: https://issues.apache.org/jira/browse/KAFKA-6546
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Major
> Fix For: 2.0.0
>
>
> In 1,1, if an endpoint is available on the broker processing a metadata
> request, but the corresponding listener is not available on the leader of a
> partition, LEADER_NOT_AVAILABLE is returned (earlier versions returned
> UNKNOWN_SERVER_ERROR). This could indicate broker misconfiguration where some
> brokers are not configured with all listeners or it could indicate a
> transient error when listeners are dynamically added, We want to treat the
> error as a transient error to process dynamic updates, but we should notify
> clients of the actual error. This change should be made when MetadataRequest
> version is updated so that LEADER_NOT_AVAILABLE is returned to older clients.
> See
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-226+-+Dynamic+Broker+Configuration]
> and [https://github.com/apache/kafka/pull/4539] for details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
