kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Javier Arias Losada <javier.ari...@gmail.com>
Subject Re: kafka connect 409 with connect-distributed
Date Mon, 12 Aug 2019 07:23:25 GMT
Hi Kafka users,

I've been trying to investigate this a bit further, in the documentation
for the Connect REST API, found this paragraph:

"*Note that if you try to modify, update or delete a resource under
> connector which may require the request to be forwarded to the leader,
> Connect will return status code 409 while the worker group rebalance is in
> process as the leader may change during rebalance.*"


I assumed that the Kafka all connect workers were able to update config,
etc through kafka and then config changes were received by the rest of
workers as messages from Kafka, but I guess that after reading this I was
wrong... are Kafka connect workers talking to each other via REST API?

If so, when there are connectivity issues such as not being able to
properly resolve the leader worker, is the REST API returning a HTTP 409?
Is that the expected behaviour?

Thank you very much
Best,
Javier arias

El jue., 8 ago. 2019 a las 14:47, Javier Arias Losada (<
javier.arilos@gmail.com>) escribió:

> Hello there,
> we were suffering some problems on our connect-distributed setup, when
> posting a new Connector config, the response was always a 409 Conflict
> mentioning a rebalance as the underlying reason.
> It was fixed after setting up a different
> CONNECT_REST_ADVERTISED_HOST_NAME on each worker, essentially after
> finding this:
> https://stackoverflow.com/questions/53730254/kafka-connect-returning-409-in-distributed-mode
>
> I wasn't able to find anything related in the documentation... can someone
> please explain the reasoning behind that behaviour?
>
> Thank you very much
> Best,
> Javier arias
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message