Skip to content

ttl: improvements to ttl usage #17040

Open
@dikshant

Description

@dikshant

We should mention that it is recommended to run TTL after every 4 hours due to gc.ttl being set to 4 hours here:
https://www.cockroachlabs.com/docs/stable/row-level-ttl.html#control-how-often-the-ttl-job-runs

Another thing we should update is that TTL uses admission control. On a cluster with no foreground traffic and a large TTL delete workload, we will see high resource usage by the TTL job. This is normal, and should there be foreground traffic, admission control will automatically throttle TTL to provide more resources to the foreground traffic.

cc: @ecwall @rafiss

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions