Flashback Garbage Collection Lifecycle

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 闪回flashback垃圾回收生命周期

| username: linnana

[TiDB Usage Environment] Test/PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]
Can the lifecycle of flashback GC recycling be freely set?

| username: linnana | Original post link

What is the default value?

| username: linnana | Original post link

This parameter? tidb_gc_max_wait_time, 24 hours.

| username: tidb菜鸟一只 | Original post link

It’s tidb_gc_life_time, but setting this value too high also carries certain risks.

| username: linnana | Original post link

Tested and found that it is the parameter tidb_gc_life_time, which performs recycling in fixed cycles.

| username: zhanggame1 | Original post link

tidb_gc_life_time is the retention time for objects. The database’s scheduled garbage collection task parameter tidb_gc_run_interval defaults to 10 minutes, meaning it checks every 10 minutes for objects that have exceeded the tidb_gc_life_time and starts the collection process.

| username: linnana | Original post link

I will find time to test and verify.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.