[
https://issues.apache.org/jira/browse/KAFKA-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Moffatt updated KAFKA-9252:
---------------------------------
Summary: Kafka Connect fails to create connector if single-broker Kafka
cluster is configured for offsets.topic.replication.factor=3 (was: Kafka
Connect )
> Kafka Connect fails to create connector if single-broker Kafka cluster is
> configured for offsets.topic.replication.factor=3
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-9252
> URL: https://issues.apache.org/jira/browse/KAFKA-9252
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 2.3.1
> Reporter: Robin Moffatt
> Priority: Minor
>
> If I mis-configure my *single* Kafka broker with
> `offsets.topic.replication.factor=3` (the default), Kafka Connect will start
> up absolutely fine (Kafka Connect started in the log file, `/connectors`
> endpoint returns HTTP 200). But if I try to create a connector, it
> (eventually) returns
> {code:java}
> {"error_code":500,"message":"Request timed out"}{code}
> There's no error in the Kafka Connect worker log at INFO level. More details:
> [https://rmoff.net/2019/11/29/kafka-connect-request-timed-out/]
> This could be improved. Either at startup ensure that the Kafka consumer
> offsets topic is available and not startup if it's not, or at least log why
> the connector failed to be created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
