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.

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

Feedback: Batch Delete Expired Data with Row-Level TTL #19333

Open
Robin-Burgess opened this issue Jan 30, 2025 · 0 comments
Open

Feedback: Batch Delete Expired Data with Row-Level TTL #19333

Robin-Burgess opened this issue Jan 30, 2025 · 0 comments

Comments

@Robin-Burgess
Copy link

Robin-Burgess commented Jan 30, 2025

Page: https://cockroachlabs.com/docs/v24.3/row-level-ttl.html

What is the reason for your feedback?

Under the ttl_select_rate_limit parameter storage description, the term 'leaseholder' is used where 'leaseholder node' would be more appropriate. In my customer's example, they have a table with 8000 ranges (and therefore 8000 leaseholders - as per the definition here) but only 6 nodes where leaseholders are placed. The ttl_select_rate_limit is calculated based on the number of nodes where leaseholders are placed (e.g. 6) rather than the number of leaseholders for the table (e.g. 8000). This caused confusion for both myself and my customer when we read it, so it would be good if this could be clarified. Thanks!

Jira issue: DOC-12194

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant