Robin Moffatt • 11/29/2019

Kafka Connect - Request timed out

This technical blog post details the diagnosis and resolution of a Kafka Connect error where creating a connector resulted in an HTTP 500 'Request timed out' with no clear logs. The root cause was a Kafka broker misconfiguration: the default offsets.topic.replication.factor of 3 was incompatible with a single-broker setup. The solution was to set the replication factor to 1, resolving the timeout.

0 comments

#configuration #error handling #distributed systems