GC: Support TiDB server with different keyspace to advance GC safe point separately #51593
Open
1 of 2 tasks
Labels
type/enhancement
The issue or PR belongs to an enhancement.
Enhancement
Support TiDB with different keyspace to advance gc separately.
Background
TiDB already supports deploying multiple clusters with different keyspaces on a single PD TiKV cluster.
Previously, we have implemented multiple TiDB clusters with a single TiDB GC Worker that does not configure Keyspace to advance the global GC safe point. Each keyspace TiDB only depends on the global GC safepoint. Do your own deleteRange cleanup.
The PR #51300 Implement that the keyspace TiDB cluster can advance the GC safe point of the current Keyspace in the Keyspace dimension by itself after enabling keyspace level GC. In this way, the GC safe points between keyspaces are separated, so that if one Keyspace GC safe point is advancing slowly, it can not affect the GC safe points of other keyspaces.
Implementation
keyspace-name
is not configured in TiDB, nothing will be changed.Related Tasks
TiDB Server support keyspace level GC
TiDB BR,Lightning,Dumpling,CDC implementation
PD interface implementation
The text was updated successfully, but these errors were encountered: