-
Notifications
You must be signed in to change notification settings - Fork 73
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
bug: Query service client not stable by SLO tests #1293
Comments
I did some tests and post below my findings. It seems like issue is not a deadlock inside pool, but timeouts in query client (possibly because of DB overload?). All tests were done by slo tester build from this PR like this:
k8s cluster has 9 nodes, with 2 cpus, 4 mem and 0.5 cpu fraction (not much but the goal wasn't to achieve some exact performance numbers). To bootstrap ydb cluster I used manifests from slo repo. Tests were performed manually without introducing any artificial failures (as automated slo test does). Tests with native-query (
|
Ideas about reason:
The text was updated successfully, but these errors were encountered: