-
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
roachtest: failover/chaos/read-only failed #119454
Comments
roachtest.failover/chaos/read-only failed with artifacts on master @ 04f0416d526a43741d22fd03966758dcccdeb79f:
Parameters:
|
roachtest.failover/chaos/read-only failed with artifacts on master @ c9c3cc5f3c3a4a6ab556f4b9d5b6ec0381901bdb:
Parameters:
|
Previously, the multiple failures were started and finished independently. This caused a problem if the ability to recover from one failure depended on a different failure recovering first. To mitigate this and to add a little more chaos, start and recover each failure in a seperate goroutine. This will allow the "most important" failure to recover first so that the others can recover if they depend on each other. Note that this is more important today while we don't support all the failure modes that the chaos implements. Specifically we don't handle partial partitions handling yet. Epic: none Fixes: cockroachdb#119085 Fixes: cockroachdb#119347 Fixes: cockroachdb#119361 Fixes: cockroachdb#119454 Release note: None
roachtest.failover/chaos/read-only failed with artifacts on master @ 9a494f4e4846a67ceea18c4b4993cefbeb19c6d9:
Parameters:
|
roachtest.failover/chaos/read-only failed with artifacts on master @ bf013ea0a5311726e65d37e8f047ce39ea2d5f10:
Parameters:
|
roachtest.failover/chaos/read-only failed with artifacts on master @ ce5f34ea97475f45fa354e58aacf424779d0de49:
Parameters:
|
roachtest.failover/chaos/read-only failed with artifacts on master @ 431d56840cacdc86638ccb48e9f3bdc16897d341:
Parameters:
|
roachtest.failover/chaos/read-only failed with artifacts on master @ 6df7436b6388eb7823b9f63a42aa75e1fbc89a85:
Parameters:
Same failure on other branches
|
roachtest.failover/chaos/read-only failed with artifacts on master @ ec9444f8287663777c5ebceff61bcd280491ba08:
Parameters:
Same failure on other branches
|
roachtest.failover/chaos/read-only failed with artifacts on master @ c43f54cdde5b7578f4a0ca61de41463f0d690993:
Parameters:
Same failure on other branches
|
119650: roachtest: make failure recovery independent r=nvanbenschoten a=andrewbaptist Previously, the multiple failures were started and finished independently. This caused a problem if the ability to recover from one failure depended on a different failure recovering first. To mitigate this, recover each failure in a separate goroutine. This will allow the "most important" failure to recover first so that the others can recover if they depend on each other. This is more important today while we don't recover from all the failure modes that chaos implements. Specifically we don't handle partial partitions fully with epoch leases. Epic: none Fixes: #119085 Fixes: #119347 Fixes: #119361 Fixes: #119454 Release note: None 122283: server: don't log for missing locality r=yuzefovich a=andrewbaptist Previously we would always log a message that the locality was unknown for requests from sql gateways. We should remove unnecessary logs from traces. Epic: none Release note: None Co-authored-by: Andrew Baptist <[email protected]>
Previously, the multiple failures were started and finished independently. This caused a problem if the ability to recover from one failure depended on a different failure recovering first. To mitigate this, recover each failure in a separate goroutine. This will allow the "most important" failure to recover first so that the others can recover if they depend on each other. This is more important today while we don't recover from all the failure modes that chaos implements. Specifically we don't handle partial partitions fully with epoch leases. Epic: none Fixes: #119085 Fixes: #119347 Fixes: #119361 Fixes: #119454 Release note: None
Previously, the multiple failures were started and finished independently. This caused a problem if the ability to recover from one failure depended on a different failure recovering first. To mitigate this, recover each failure in a separate goroutine. This will allow the "most important" failure to recover first so that the others can recover if they depend on each other. This is more important today while we don't recover from all the failure modes that chaos implements. Specifically we don't handle partial partitions fully with epoch leases. Epic: none Fixes: #119085 Fixes: #119347 Fixes: #119361 Fixes: #119454 Release note: None
roachtest.failover/chaos/read-only failed with artifacts on master @ e50b0ec4d3a53f81e26f3776ae3f3be55d435a9a:
Parameters:
ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=2
ROACHTEST_encrypted=false
ROACHTEST_fs=ext4
ROACHTEST_localSSD=false
ROACHTEST_metamorphicBuild=false
ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
This test on roachdash | Improve this report!
Jira issue: CRDB-36206
The text was updated successfully, but these errors were encountered: