Keep resolvedTs lag and checkpoint lag in metrics have the same meaning as the old ticdc arch
Open
Nobody has claimed this yet.
type/feature-request
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
In order to ensure the uniformity of the ticdc external performance, we need to ensure that resolvedTs in metrics reflects the progress of data changes pushed to the cdc；checkpointTs reflects the progress of data pushed to the downstream.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the metric definitions and update paths for resolvedTs and checkpointTs, then compare their meanings with the old TiCDC architecture. Done means resolvedTs represents progress of data changes pushed to CDC and checkpointTs represents progress of data pushed downstream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data-engineering, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100