-
Notifications
You must be signed in to change notification settings - Fork 552
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
Ci Failure (Failed to get metadata: Local: Timed out) in ThroughputLimitsSnc
.test_configuration
#8809
Comments
Egress TP limit is set by the test to 64 B/s. Controller log leader gets this sequence of KAPI requests:
12.6s is too much for the client and it times out the metadata request. As a mitigation, I will double the minimum egress TP limit. |
Fixes redpanda-data#8809 Double the minimum tested value for TP limit (both ingress and egress) because there is evidence that 64 B/s on egress side cause timeouts while a client connects to the cluster.
Happened again in CDT: https://buildkite.com/redpanda/vtools/builds/7321#0187c490-ccb8-4b5c-89bc-a3d4ebd3ee93 128 B/s still seems to be on the edge, needs a bump to 256 B/s |
Double the minimum tested value for TP limit (both ingress and egress) because there is evidence that 128 B/s is still close to the edge and may fail the test when used for both ingress and egress. Fixes redpanda-data#8809
Double the minimum tested value for TP limit (both ingress and egress) because there is evidence that 128 B/s is still close to the edge and may fail the test when used for both ingress and egress. Fixes redpanda-data#8809
Double the minimum tested value for TP limit (both ingress and egress) because there is evidence that 128 B/s is still close to the edge and may fail the test when used for both ingress and egress. Fixes redpanda-data#8809 (cherry picked from commit 6b439c4)
Double the minimum tested value for TP limit (both ingress and egress) because there is evidence that 128 B/s is still close to the edge and may fail the test when used for both ingress and egress. Fixes redpanda-data#8809
@BenPope - this is still happening and as you see there has been a history of just bumping the limit which hasn't panned out (yet?). As you are planning big changes in this area I figure this failure may be obsoleted by them, so looking into it is probably fruitless in light of that. I guess after you changes go in and this hasn't happened for a while we can simply close it. WDYT? |
I'm going to mark this as sev/low and point at the epic https://github.com/redpanda-data/core-internal/issues/917 |
This makes sense to me. |
Version & Environment
Redpanda version:
dev
:This happened during cluster startup in CI
https://buildkite.com/redpanda/redpanda/builds/22997#01863c84-7997-4df4-a53b-3be8d31d445d/6-2309
The text was updated successfully, but these errors were encountered: