pingcap / pingcap/tidb

keyspace: gc delete range

Open
#40,848 0 comments 0 reactions 0 assignees View on GitHub
type/feature-request
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Feature Request

**Is your feature request related to a problem? Please describe:**

If set keyspace-name , different keyspace-name user has their own mysql.gc_delete_range table, so they need do delege range by themself.

**Describe the feature you'd like:**

1. Each keyspace has one 'delete range GC Worker' owner, to call the delete range gc logic of keyspace.
2. The whole cluster has a GC Worker to calculate gc safepoint and do resolve locks.

**Describe alternatives you've considered:**

I once wanted to get all keyspaces in GC Worker which is responsible for calculating GC safepoint, and trigger the delete range of each keyspace. But, switching between different keyspaces in a process and using session will cause compatibility problems.

**Teachability, Documentation, Adoption, Migration Strategy:**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.