Details
-
Bug
-
Status: Reopened
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
If a connector fails during startup, it will never be added to the worker's internal list of running connectors (see https://github.com/apache/kafka/blob/87260a33b01590d0f73577840422e24fa589bed0/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/Worker.java#L298), and the same happens for tasks (see https://github.com/apache/kafka/blob/87260a33b01590d0f73577840422e24fa589bed0/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/Worker.java#L570).
This leads to the following WARN-level log messages when that connector/task is scheduled to be stopped by the worker:
- Ignoring stop request for unowned connector <name>
- Ignoring await stop request for non-present connector <name>
- Ignoring stop request for unowned task <name>
- Ignoring await stop request for non-present task <name>
If the connector/task failed on startup, there should already be log messages detailing the failure and its cause; there is no need to emit warning messages about not stopping that connector when it is scheduled for shutdown. Even worse, emitting these messages may cause users to believe that their cluster is experiencing a rebalancing bug that is somehow causing connectors/tasks that are not assigned to a worker to be revoked from it.
Attachments
Issue Links
- links to