After the CDC task fails, tikv_gc_safe_point does not update

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: cdc任务失败之后,tikv_gc_safe_point一直不更新

| username: TiDBer_7E0yINhK

[TiDB Usage Environment] Production Environment
[TiDB Version] 5.1.1
[Encountered Problem] After the CDC task fails, manually removing the task causes tikv_gc_safe_point to not update.
[Reproduction Path]
Start CDC, encounter ErrGCTTLExceeded error
Manually remove the task, find that it cannot be removed (known issue: changefeed can't be removed when meeting ErrGCTTLExceeded error · Issue #2391 · pingcap/tiflow · GitHub)
[Problem Phenomenon and Impact]
The tikv_gc_safe_point remains at that time point. Will this cause any issues for the cluster?
Observing the monitoring gc_worker_actions, there is data every 10 minutes.

| username: Billmay表妹 | Original post link

Have you considered upgrading the version?

| username: Billmay表妹 | Original post link

Refer to this article: 专栏 - TiDB集群的GC不回收案例(案情二) | TiDB 社区

| username: TiDBer_7E0yINhK | Original post link

Okay, thank you. I checked that mysql.tidb tikv_gc_last_run_time is updating normally, and gc_speed is also not zero. Can I understand that GC is running normally?
So what method should I use to let tikv_gc_safe_point continue to advance, or is there any way to remove the failed CDC task?

| username: asddongmen | Original post link

It is recommended to upgrade the CDC version to solve the problem.

| username: TiDBer_CEVsub | Original post link

It might be because the data volume hasn’t changed, leading to no changes in RocksDB’s compaction.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.