pingcap/tiflow

ticdc: improve error message when downstream kafka is unavailable

Open

#11,540 opened on Aug 29, 2024

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)Go (310 forks)auto 404
affects-7.5good first issueseverity/minortype/enhancement

Repository metrics

Stars
 (461 stars)
PR merge metrics
 (PR metrics pending)

Description

When downstream kafka is unavailable, kafka sink will try to restart. After several restart, it will report an error like "table sink stuck".
The error message doesn't explain what happened and is useless to help customer to locate the problem, so we need to imporve this error message to explain the cause of the problem.

Contributor guide

Research direction
Locate the code that produces the 'table sink stuck' error in TiCDC Kafka sink. Trace the restart logic to understand when this error is triggered. Improve the error message to include the reason (e.g., downstream Kafka unavailable) and possibly the underlying error. Look for related tests and update them if needed.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75