pingcap / pingcap/ticdc

ticdc panic with "CommitTs must be greater than the resolvedTs"

Open
#1,870 0 comments 0 reactions 1 assignee View on GitHub

@lidezhu is already working on this.

Since Sep 1, 2025.

ga-optional type/bug
Dominant language
Go
Stars
56
Forks
63
Avg merge
2d 20h
Merged PRs (30d)
34

Description

What did you do?

Run test flashback_during_cdc_running

What did you expect to see?

Test pass

What did you see instead?

Test fail with error:
[2025/08/28 03:54:44.212 +00:00] [FATAL] [region_event_handler.go:234] ["The CommitTs must be greater than the resolvedTs"] [EventType=COMMITTED] [CommitTs=460417430761242655] [resolvedTs=460417475246817305] [regionID=2688] [stack="github.com/pingcap/ticdc/logservice/logpuller.handleEventEntries\n[tgithub.com/pingcap/ticdc/logservice/logpuller/region_event_handler.go:234](http://tgithub.com/pingcap/ticdc/logservice/logpuller/region_event_handler.go:234)\[ngithub.com/pingcap/ticdc/logservice/logpuller.(*regionEventHandler).Handle](http://ngithub.com/pingcap/ticdc/logservice/logpuller.(*regionEventHandler).Handle)\n\[tgithub.com/pingcap/ticdc/logservice/logpuller/region_event_handler.go:88](http://tgithub.com/pingcap/ticdc/logservice/logpuller/region_event_handler.go:88)\[ngithub.com/pingcap/ticdc/utils/dynstream.(*stream[...]).handleLoop](http://ngithub.com/pingcap/ticdc/utils/dynstream.(*stream[...]).handleLoop)\n\[tgithub.com/pingcap/ticdc/utils/dynstream/stream.go:251](http://tgithub.com/pingcap/ticdc/utils/dynstream/stream.go:251)"]

Versions of the cluster

Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

(paste TiDB cluster version here)

Upstream TiKV version (execute tikv-server --version):

(paste TiKV version here)

TiCDC version (execute cdc version):

(paste TiCDC version here)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.