-
-
Notifications
You must be signed in to change notification settings - Fork 221
Open
Labels
status/triage/completedAutomatic triage completedAutomatic triage completedstatus/triage/manualManual triage in progressManual triage in progresstype/bugSomething isn't workingSomething isn't working
Description
Issue submitter TODO list
- I've looked up my issue in FAQ
- I've searched for an already existing issues here
- I've tried running
main-labeled docker image and the issue still persists there - I'm running a supported version of the application which is listed here
Describe the bug (actual behavior)
Hello,
Since the latest version 1.4.2, it has become less clear when a Kafka Connect connector is in a FAILED state. As shown in the attached screenshot, the connector is displayed as RUNNING with a warning, while inside the connector details the actual status is FAILED.
Is there a specific reason why the connector status is not shown as FAILED, as it was in previous versions?
Is this expected behavior, or is it a regression?
Thank you for your help.
Have a great day.
Expected behavior
My expectation is that the connector’s main status should also be shown as FAILED when the detailed view reports it as such, which is how it behaved in earlier versions.
Your installation details
1.4.2
Debezium connector
Steps to reproduce
See the connector status in the kafka connect with 1 connector fail
Screenshots
Logs
No response
Additional context
No response
Metadata
Metadata
Assignees
Labels
status/triage/completedAutomatic triage completedAutomatic triage completedstatus/triage/manualManual triage in progressManual triage in progresstype/bugSomething isn't workingSomething isn't working