-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
roachtest: kv/gracefuldraining failed #130760
Comments
This is like #130747 - right at the beginning of the test, when we take a node down gracefully, throughput takes a hit. |
130796: roachtest: improve observability in kv/gracefuldraining r=andrewbaptist a=tbg This test sometimes fails since QPS tanks in the aftermath of a gracefully shut down node. This commit adds a one-minute warm-up period during which stats are collected and sets up statement bundle collection. The hope is that future failures will have complete traces of a number of failed requests, which should make it easy to understand why throughput was adversely affected. Fixes #130747. Touches #130760 (release-24.2; needs backport) Release note: None Epic: None Co-authored-by: Tobias Grieger <[email protected]>
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 7a32a78a1f7a691f32a131d79f6ae00a19e20e86:
Parameters:
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 6151abc4225aecfe5f5fc4655b619d560226777a:
Parameters:
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ a245c3f2811e01c9d51eae75612ccd5a6d406464:
Parameters:
|
I'm going to remove my assignment -- as this involvement was primarily triage related. If the test fails again with the CPU profiles available, I'll take a look. |
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 2b75ba5e0a0793b946e8ae43ddf671cbd3ea1a5f:
Parameters:
Same failure on other branches
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 134112c2d6920bd50d93d1d73596a34a477070b6:
Parameters:
Same failure on other branches
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 93b67a9956891893444de8e20eb2a22c5ad55624:
Parameters:
Same failure on other branches
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 2112e82243d0f454e659236dbf76937ce73dc013:
Parameters:
Same failure on other branches
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ c9c36aba9df73ce233967020efd5b96e1992378a:
Parameters:
Same failure on other branches
|
Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout. roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 5764366875adca70c3a3ff3d4d13aaf599bc53a7:
Parameters:
Same failure on other branches
|
Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout. roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 5764366875adca70c3a3ff3d4d13aaf599bc53a7:
Parameters:
Same failure on other branches
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ be69012d37da70d0ada6eb4cf2b008d02ef16ffd:
Parameters:
Same failure on other branches
|
Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout. roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ c9b7151258520849effaa3abd9514f00fb240039:
Parameters:
Same failure on other branches
|
Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout. roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 1ba69a2843ef6f3ffdd8a3863de571342aa501eb:
Parameters:
Same failure on other branches
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ fdb6c4cd2758a1b915e5815bce30dde3616b7ff9:
Parameters:
Same failure on other branches
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ b7aadefdfe99a5ca617a6d73c14915a494be8128:
Parameters:
Same failure on other branches
|
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 3428b140d7f5019b89e37164ca6c2fb3af981727:
Parameters:
Same failure on other branches
|
Closing now that the metrics interval PR has been backported. #131569 (comment). |
roachtest.kv/gracefuldraining failed with artifacts on release-24.2 @ 3542ba5a3f47f9042e81583fe52c893aac9c4e3c:
Parameters:
ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_metamorphicBuild=false
ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-42211
The text was updated successfully, but these errors were encountered: