Description
Connector Herder throws ConnectException and shutdown if sent a wrong config, restarting herder will keep failing with the wrong config; It make sense that herder should stay available when start connector or task failed; After receiving a delete connector request, the herder can delete the wrong config from "config storage"
Attachments
Issue Links
- is duplicated by
-
KAFKA-3759 Incorrect JDBC credentials cause Connect worker to permanently fail
- Resolved
- is related to
-
KAFKA-4042 DistributedHerder thread can die because of connector & task lifecycle exceptions
- Resolved
- links to