provectus/kafka-ui

Invalid KC task state upon a restart

Open

#1890 opened on Apr 24, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (7,799 stars) (977 forks)batch import
good first issuescope/backendstatus/acceptedtype/bug

Description

Describe the bug

After Restart failed Task in a connector with failed tasks the State is still FAILED but the Tasks Failed is 0 at the same time, even if switch the tab to Tasks and return in the connector. In my case both indicators matched after return to Connectors overview (however it could be just coincidence and the state needed some time).

Set up

https://www.kafka-ui.provectus.io/

Steps to Reproduce Steps to reproduce the behavior:

  1. Navigate to local/Connectors
  2. Click some connector with state Failed
  3. Push the button Restart failed Task
  4. Observe differente status for the same indicator - State is still FAILED but the Tasks Failed is 0 at the same time

Expected behavior

State is RUNNING and the Tasks Failed is 0 at the same time after Restart failed Task Screenshots

Additional context

Contributor guide

Tech stack
javareactjavascript
Domain
full stack
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaReactKafka basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the connector details page component to understand how connector state and tasks failed count are displayed. Review the Kafka Connect REST API responses for restarting failed tasks and ensure the frontend correctly updates state after the restart. Check if the issue is a frontend state management problem or a backend inconsistency. Look at existing tests for connector operations.