[GitHub] [kafka] akatona84 commented on pull request #11565: KAFKA-13504: Retry connect internal topics' creation in case of InvalidReplicationFactorException

[GitBox <gi...@apache.org>]

akatona84 commented on PR #11565:
URL: https://github.com/apache/kafka/pull/11565#issuecomment-1185959070

   I totally agree that I have too many configs :D
   
   Yeah, it's happening quite often when testing, just starting the brokers and connect cluster and the health check of connect alerts due to its unexpected death.
   I know it should be the orchestrator's duty to start connect after brokers are fine, yet thought would be nice to make it more robust.
   Now I tried to rebase and see KIP-618 efforts on trunk, will try again to rebase and rewrite it to time bound retries. It would still need two configs: the timeout and the backoff as I see default.api.timeout.ms is not defined for the worker/distributed.
   
   tbh I'm not 100% sure if this robustness worth the effort, I'll think about it.


-- 
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.

To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org