[
https://issues.apache.org/jira/browse/KAFKA-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950345#comment-16950345
]
ASF GitHub Bot commented on KAFKA-9035:
---------------------------------------
ivanyu commented on pull request #7506: KAFKA-9035: Improve logging on
potential loop forwaring in Kafka Connect REST
URL: https://github.com/apache/kafka/pull/7506
These two PRs make Kafka Connect warn the user when there's a possibility of
redirecting REST requests from a Connect worker to itself.
*Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.*
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
