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.

Sign up for GitHub

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

Jump to bottom

GC bind record with deleted status #26191

Closed
Tracked by #25970
eurekaka opened this issue Jul 13, 2021 · 0 comments · Fixed by #26206
Closed
Tracked by #25970

GC bind record with deleted status #26191

eurekaka opened this issue Jul 13, 2021 · 0 comments · Fixed by #26206
Assignees
@eurekaka
Labels
epic/sql-plan-management sig/planner SIG: Planner type/enhancement The issue or PR belongs to an enhancement.

Comments

@eurekaka
Copy link
Contributor

Enhancement

Currently, DROP GLOBAL BINDING would only mark the bind as deleted, i.e, it is not physically removed from mysql.bind_info since we rely on its update_time column for incremental synchronization of the bind record to all tidb servers. Hence in the long run, the number of rows in mysql.bind_info would become larger and larger. We decide to internally GC those bind records with deleted status, and the update_time is 10 leases ago, which means that these records are supposed to be synced by all tidb servers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eurekaka eurekaka

Labels
epic/sql-plan-management sig/planner SIG: Planner type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

bindinfo: garbage collect deleted bind records eurekaka/tidb
1 participant
@eurekaka