coordinator: fix incorrect changefeed status when resuming changefeed

[wk989898]

What problem does this PR solve?

Issue Number: close #3557 ref #1644

What is changed and how it works?

• Changefeed Resumption Logic: Modified the ResumeChangefeed function in etcd_backend.go to explicitly set the Progress field of the changefeed status to config.ProgressNone when a changefeed is resumed. This ensures that progress tracking is reset or initialized correctly upon resumption.
• Stop Changefeed Operator: Wait for the operator to finish after executing api call

Check List

Tests

• Unit test
• Integration test

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

`None`.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[gemini-code-assist]

Summary of Changes

Hello @wk989898, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the state management of changefeeds within the TiCDC coordinator. Specifically, it addresses how a changefeed's progress is handled when it transitions from a paused to a running state, aiming to ensure a clean and accurate restart of progress tracking upon resumption.

Highlights

• Changefeed Resumption Logic: Modified the ResumeChangefeed function in etcd_backend.go to explicitly set the Progress field of the changefeed status to config.ProgressNone when a changefeed is resumed. This ensures that progress tracking is reset or initialized correctly upon resumption.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request modifies the ResumeChangefeed function in coordinator/changefeed/etcd_backend.go to set the status.Progress field to config.ProgressNone when a changefeed is resumed. There are no review comments provided for this change.

[wk989898]

/test all

[tenfyzhong]

/retest

[wk989898]

/check-issue-triage-complete

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongyunyan, lidezhu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [hongyunyan,lidezhu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-12-16 03:27:52.689013595 +0000 UTC m=+1530017.502791167: ☑️ agreed by hongyunyan.
• 2025-12-16 03:28:47.642840209 +0000 UTC m=+1530072.456617782: ☑️ agreed by lidezhu.

[wk989898]

/retest

[wk989898]

/test pull-cdc-kafka-integration-heavy

[ti-chi-bot]

@wk989898: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cdc-mysql-integration-heavy	2d7de6a	link	unknown	/test pull-cdc-mysql-integration-heavy

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.