[
https://issues.apache.org/jira/browse/KAFKA-15408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Pang updated KAFKA-15408:
---------------------------------
Description:
h2. Issue
Currently, Kafka Connect just reports failed tasks on REST API, with the error.
Users are expected to monitor the status and restart individual connectors if
there is transient errors. Unfortunately these are common for database
connectors, e.g. transient connection error, flip of DNS, database downtime,
etc. Kafka Connect silently failing due to these scenarios would lead to stale
data downstream.
h2. Proposal
Kafka Connect should be able to restart failed tasks automatically, up to a
configurable max-tries.
h2. Prior arts
*
[https://github.com/strimzi/proposals/blob/main/007-restarting-kafka-connect-connectors-and-tasks.md]
*
[https://docs.aiven.io/docs/products/kafka/kafka-connect/howto/enable-automatic-restart]
was:
h2. Issue
Currently, Kafka Connect just reports failed tasks on REST API, with the error.
Users are expected to monitor the status and restart individual connectors if
there is transient errors. Unfortunately these are common for database
connectors, e.g. transient connection error, flip of DNS, database downtime,
etc. Kafka Connect silently failing due to these scenarios would lead to stale
data downstream.
h2. Proposal
Kafka Connect should be able to restart failed tasks automatically, up to a
configurable max-tries.
> Restart failed tasks in Kafka Connect up to a configurable max-tries
> --------------------------------------------------------------------
>
> Key: KAFKA-15408
> URL: https://issues.apache.org/jira/browse/KAFKA-15408
> Project: Kafka
> Issue Type: New Feature
> Components: KafkaConnect
> Reporter: Patrick Pang
> Priority: Major
>
> h2. Issue
> Currently, Kafka Connect just reports failed tasks on REST API, with the
> error. Users are expected to monitor the status and restart individual
> connectors if there is transient errors. Unfortunately these are common for
> database connectors, e.g. transient connection error, flip of DNS, database
> downtime, etc. Kafka Connect silently failing due to these scenarios would
> lead to stale data downstream.
> h2. Proposal
> Kafka Connect should be able to restart failed tasks automatically, up to a
> configurable max-tries.
> h2. Prior arts
> *
> [https://github.com/strimzi/proposals/blob/main/007-restarting-kafka-connect-connectors-and-tasks.md]
>
> *
> [https://docs.aiven.io/docs/products/kafka/kafka-connect/howto/enable-automatic-restart]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
