[
https://issues.apache.org/jira/browse/KAFKA-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Yurchenko updated KAFKA-9035:
----------------------------------
Summary: Improve logging on potential loop forwaring in Kafka Connect REST
(was: Improve )
> Improve logging on potential loop forwaring in Kafka Connect REST
> -----------------------------------------------------------------
>
> Key: KAFKA-9035
> URL: https://issues.apache.org/jira/browse/KAFKA-9035
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.2.0, 2.1.1, 2.3.0, 2.2.1
> Reporter: Ivan Yurchenko
> Assignee: Ivan Yurchenko
> Priority: Minor
>
> Kafka Connect workers in the distributed mode can be set up so that they have
> the same advertised URL (e.g.
> {{[http://127.0.0.1:8083|http://127.0.0.1:8083/]}}). When a request (e.g.,
> for connector creation) lands on a worker that is not the leader, it will be
> forwarded to the leader's advertised URL. However, if advertised URLs are all
> the same, it might never reach the leader (due to the limited number of
> forwards). (See https://issues.apache.org/jira/browse/KAFKA-7121 for an
> example.)
> I propose to address this by detecting such a situation and warning the user
> on the log.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
