Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

puller: close kvclient correctly when stopping a processor (#11957) #11981

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #11957

What problem does this PR solve?

Issue Number: close #11954

What is changed and how it works?

When stopping a processor, close the associated puller.

Check List

Tests

  • Manual test (add detailed scripts or steps below)
[2024/12/31 16:21:32.261 +08:00] [INFO] [multiplexing_puller.go:331] ["MultiplexingPuller exits"] [namespace=default] [changefeed=x3_owner_ddl_puller]
[2024/12/31 16:21:32.270 +08:00] [INFO] [multiplexing_puller.go:366] ["MultiplexingPuller is closed"] [namespace=default] [changefeed=x3_owner_ddl_puller]
[2024/12/31 16:21:32.273 +08:00] [INFO] [multiplexing_puller.go:331] ["MultiplexingPuller exits"] [namespace=default] [changefeed=x3]
[2024/12/31 16:21:32.273 +08:00] [INFO] [multiplexing_puller.go:366] ["MultiplexingPuller is closed"] [namespace=default] [changefeed=x3]
[2024/12/31 16:21:32.273 +08:00] [INFO] [multiplexing_puller.go:331] ["MultiplexingPuller exits"] [namespace=default] [changefeed=x3_processor_ddl_puller]
[2024/12/31 16:21:32.273 +08:00] [INFO] [multiplexing_puller.go:366] ["MultiplexingPuller is closed"] [namespace=default] [changefeed=x3_processor_ddl_puller]

With the patch, when removing a changefeed, all pullers for owner_ddl, processor_ddl and source_manager are closed.
No goroutine leak happens any more.

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 ti-chi-bot added lgtm release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-7.5 This PR is cherry-picked to release-7.5 from a source PR. labels Jan 6, 2025
Signed-off-by: qupeng <[email protected]>
@ti-chi-bot ti-chi-bot bot added cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved labels Jan 7, 2025
Copy link
Contributor

ti-chi-bot bot commented Jan 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hicqu

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

The pull request process is described here

Needs approval from an approver in each of these files:

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 ti-chi-bot bot added the approved label Jan 7, 2025
@hicqu
Copy link
Contributor

hicqu commented Jan 14, 2025

/retest

2 similar comments
@hicqu
Copy link
Contributor

hicqu commented Jan 14, 2025

/retest

@hicqu
Copy link
Contributor

hicqu commented Jan 20, 2025

/retest

@ti-chi-bot ti-chi-bot bot merged commit 9ef86ba into pingcap:release-7.5 Jan 20, 2025
13 checks passed
@hicqu hicqu deleted the cherry-pick-11957-to-release-7.5 branch January 22, 2025 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherry-pick-approved Cherry pick PR approved by release team. lgtm release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-7.5 This PR is cherry-picked to release-7.5 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants