-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
catalog/lease: timeout during lease acquisition #119897
Comments
It seems like this and #119898 are using a disk-based configuration for the test cluster, and the cache size is the default 128MiB. That might explain the signs of slowdowns in the logs, since CPU, goroutines, and memory all seem pretty normal. That being said, it seems problematic that some disk-related slowdowns could cause an internal error during lease acquisition. @cockroachdb/sql-foundations should these code paths handle errors more gracefully? Here's the stack trace from the logs:
|
|
+cc @cockroachdb/sql-foundations It looks like the lease acquisition timeouts from #116904 are resurfacing here. |
the reason for the internal error is that the context used for authenticating has a 10 second deadline. if this lease timeout only appears underneath i created cockroachdb/cockroach-go#177 to improve the cache size settings and avoid slowdowns. |
pkg/sql/logictest/tests/cockroach-go-testserver-23.2/cockroach-go-testserver-23_2_test.TestLogic_mixed_version_can_login failed with artifacts on master @ bf013ea0a5311726e65d37e8f047ce39ea2d5f10:
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-36372
The text was updated successfully, but these errors were encountered: