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

sql/catalog/lease: increase sql.tablecache.lease.refresh_limit to 500 #59319

Conversation

ajwerner
Copy link
Contributor

@ajwerner ajwerner commented Jan 22, 2021

The cluster setting sql.tablecache.lease.refresh_limit is used to decide
how many leases the sql descriptor lease manager will refresh every interval,
which is defined by the sql table lease duration (and is very much static).

This increase means that we'll refresh up to this many leases per node every
~2.5 minutes. There's already a semaphore in place to ensure that the
concurrency is not more than 5 per node. This has become ever more important
as more people are using cockroach with larger schemas. It's also become more
important because descriptors, schemas, and types are also leased.

Fixes #59316.

Release note (general change): Increased the default value of
sql.tablecache.lease.refresh_limit to 500 in order to accomodate larger
schemas without encountering RETRY_COMMIT_DEADLINE_EXCEEDED errors and
generally higher latency.

The cluster setting `sql.tablecache.lease.refresh_limit` is used to decide
how many leases the sql descriptor lease manager will refresh every interval,
which is defined by the sql table lease duration (and is very much static).

This increase means that we'll refresh up to this many leases per node every
~2.5 minutes. There's already a semaphore in place to ensure that the
concurrency is not more than 5 per node. This has become ever more important
as more people are using cockroach with larger schemas. It's also become more
important because descriptors, schemas, and types are also leased.

Release note (general change): Increased the default value of
`sql.tablecache.lease.refresh_limit` to 500 in order to accomodate larger
schemas without encountering `RETRY_COMMIT_DEADLINE_EXCEEDED` errors and
generally higher latency.
@ajwerner ajwerner requested review from jordanlewis and a team January 22, 2021 22:23
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor

@thoszhang thoszhang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 1 of 1 files at r1.
Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @jordanlewis)

Copy link
Member

@jordanlewis jordanlewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm thanks!

@ajwerner
Copy link
Contributor Author

TFTR!

bors r+

@craig
Copy link
Contributor

craig bot commented Jan 23, 2021

Build succeeded:

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

Successfully merging this pull request may close these issues.

sql: consider increasing the default maximum number of leases to refresh
4 participants