roachtest: follower-reads/mixed-version/single-region failed #129546
Assignees
Labels
branch-master
Failures and bugs on the master branch.
branch-release-24.3
Used to mark GA and release blockers, technical advisories, and bugs for 24.3
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
P-2
Issues/test failures with a fix SLA of 3 months
T-kv
KV Team
Comments
cockroach-teamcity
added
branch-master
andrewbaptist
added
the
C-bug
|
This one seems to be because of shared process multi-tenancy. From the logs: Seems like we're using #129167 as the main issue for this class of failures, so I'll mark this as a duplicate. We're also not treating these shared process multi-tenancy failures as release blockers, so I'll remove the label. |
arulajmani
removed
the
release-blocker
|
roachtest.follower-reads/mixed-version/single-region failed with artifacts on master @ 8551145a0c99c4c95a28ec470e699d0c20ca97ab: Parameters:
Help
See: roachtest README See: How To Investigate (internal) Grafana is not yet available for azure clusters |
|
roachtest.follower-reads/mixed-version/single-region failed with artifacts on master @ 67e99ebec74c1f6a6dfbf1cc0bca2d255a55f867: Parameters:
Help
See: roachtest README See: How To Investigate (internal) Grafana is not yet available for azure clusters |
|
roachtest.follower-reads/mixed-version/single-region failed with artifacts on master @ 197c6ee5537ffb211ebd8dbcbe49edc6d5c710e1: Parameters:
Help
See: roachtest README See: How To Investigate (internal) Grafana is not yet available for azure clusters |
|
roachtest.follower-reads/mixed-version/single-region failed with artifacts on master @ 83589fb87caa92fb42e83994f1691978f37e4cbb: Parameters:
|
|
roachtest.follower-reads/mixed-version/single-region failed with artifacts on master @ 8e6e4090457565a41bc3bd8ea954e437030d1c49: Parameters:
|
|
roachtest.follower-reads/mixed-version/single-region failed with artifacts on master @ ec2573dc6aaeefc226440bb2c5a7c94a63989868: Parameters:
|
|
roachtest.follower-reads/mixed-version/single-region failed with artifacts on master @ 4de315c9ca4ccf7c3bdbf53a5226e8c14c84a68e: Parameters:
|
arulajmani
added
P-2
andrewbaptist
added a commit
to andrewbaptist/cockroach
that referenced
this issue
Oct 21, 2024
After introducing shared process testing of follower reads, the tests follower-reads/mixed-version/* have been flaky. This commit starts testing from 23.2 to make sure that any other failures are caught and triaged correctly. Epic: none Fixes: cockroachdb#133000 Fixes: cockroachdb#132999 Fixes: cockroachdb#129546 Fixes: cockroachdb#129167 Release note: None
andrewbaptist
added a commit
to andrewbaptist/cockroach
that referenced
this issue
Oct 21, 2024
After introducing shared process testing of follower reads, the tests follower-reads/mixed-version/* have been flaky. This commit starts testing from 23.2 to make sure that any other failures are caught and triaged correctly. Epic: none Fixes: cockroachdb#133000 Fixes: cockroachdb#132999 Fixes: cockroachdb#129546 Fixes: cockroachdb#129167 Release note: None
craig bot
pushed a commit
that referenced
this issue
Oct 23, 2024
132851: kvserver/rangefeed: remove context from kvpb.RangeFeedEventSink r=stevendanna a=wenyihu6 Previously, `node.MuxRangefeed` created a child context for each rangefeed request, storing it in the stream interface to allow the node level to be able to shut down registration goroutines. This patch simplifies the approach by passing the stream context directly to `p.Register`, eliminating the need to store context in `streamSink` or return context via the interface. So this patch also removes context from `kvpb.RangeFeedEventSink`. Epic: none Release note: none 133092: roachtest: disable 23.1 -> 23.2 testing for follower reads r=arulajmani a=andrewbaptist After introducing shared process testing of follower reads, the tests follower-reads/mixed-version/* have been flaky. This commit starts testing from 23.2 to make sure that any other failures are caught and triaged correctly. Epic: none Fixes: #133000 Fixes: #132999 Fixes: #129546 Fixes: #129167 Release note: None Co-authored-by: Wenyi Hu <[email protected]> Co-authored-by: Andrew Baptist <[email protected]>
craig bot
pushed a commit
that referenced
this issue
Oct 23, 2024
132443: crosscluster/logical: add KV write path metrics r=msbutler a=stevendanna It would be nice to know how often we are hitting these particular errors. Epic: none Release note: None 133092: roachtest: disable 23.1 -> 23.2 testing for follower reads r=arulajmani a=andrewbaptist After introducing shared process testing of follower reads, the tests follower-reads/mixed-version/* have been flaky. This commit starts testing from 23.2 to make sure that any other failures are caught and triaged correctly. Epic: none Fixes: #133000 Fixes: #132999 Fixes: #129546 Fixes: #129167 Release note: None 133273: ui: bump cluster-ui to 24.3.0-prerelease.4 r=xinhaoz a=xinhaoz This commit bumps cluster-ui version to 24.3.0-prerelease.4 and moves crdb-protobuf-client pkg from dependencies back to dev dependencies in an attempt to resolve build issues when exporting the package. Epic: none Release note: None Co-authored-by: Steven Danna <[email protected]> Co-authored-by: Andrew Baptist <[email protected]> Co-authored-by: Xin Hao Zhang <[email protected]>
![blathers[crl]](https://avatars.githubusercontent.com/in/59700?s=40&u=373d9101a12edc3847d2fb6ae78e3adcfb4ca41e&v=4){kind=avatar}
|
Based on the specified backports for linked PR #133092, I applied the following new label(s) to this issue: branch-release-24.3. Please adjust the labels as needed to match the branches actually affected by this issue, including adding any known older branches. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
blathers-crl
bot
added
the
branch-release-24.3
blathers-crl bot
pushed a commit
that referenced
this issue
Oct 23, 2024
After introducing shared process testing of follower reads, the tests follower-reads/mixed-version/* have been flaky. This commit starts testing from 23.2 to make sure that any other failures are caught and triaged correctly. This test is flaky when upgrading from v23.1 to v23.2 for follower reads in shared-process deployments. There were a number of changes to tenant health checks since then which appear to have addressed this issue. Epic: none Fixes: #133000 Fixes: #132999 Fixes: #129546 Fixes: #129167 Release note: None
miraradeva
pushed a commit
to miraradeva/cockroach
that referenced
this issue
Dec 11, 2024
After introducing shared process testing of follower reads, the tests follower-reads/mixed-version/* have been flaky. This commit starts testing from 23.2 to make sure that any other failures are caught and triaged correctly. This test is flaky when upgrading from v23.1 to v23.2 for follower reads in shared-process deployments. There were a number of changes to tenant health checks since then which appear to have addressed this issue. Epic: none Fixes: cockroachdb#133000 Fixes: cockroachdb#132999 Fixes: cockroachdb#129546 Fixes: cockroachdb#129167 Release note: None
miraradeva
pushed a commit
to miraradeva/cockroach
that referenced
this issue
Dec 11, 2024
After introducing shared process testing of follower reads, the tests follower-reads/mixed-version/* have been flaky. This commit starts testing from 23.2 to make sure that any other failures are caught and triaged correctly. This test is flaky when upgrading from v23.1 to v23.2 for follower reads in shared-process deployments. There were a number of changes to tenant health checks since then which appear to have addressed this issue. Epic: none Fixes: cockroachdb#133000 Fixes: cockroachdb#132999 Fixes: cockroachdb#129546 Fixes: cockroachdb#129167 Release note: None
miraradeva
pushed a commit
that referenced
this issue
Dec 12, 2024
After introducing shared process testing of follower reads, the tests follower-reads/mixed-version/* have been flaky. This commit starts testing from 23.2 to make sure that any other failures are caught and triaged correctly. This test is flaky when upgrading from v23.1 to v23.2 for follower reads in shared-process deployments. There were a number of changes to tenant health checks since then which appear to have addressed this issue. Epic: none Fixes: #133000 Fixes: #132999 Fixes: #129546 Fixes: #129167 Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
roachtest.follower-reads/mixed-version/single-region failed with artifacts on master @ c57e04527fbe285402bcadb7f73ce559e85d0c27:
Parameters:
ROACHTEST_arch=amd64ROACHTEST_cloud=azureROACHTEST_coverageBuild=falseROACHTEST_cpu=2ROACHTEST_encrypted=falseROACHTEST_fs=ext4ROACHTEST_localSSD=trueROACHTEST_runtimeAssertionsBuild=falseROACHTEST_ssd=0Help
See: roachtest README
See: How To Investigate (internal)
Grafana is not yet available for azure clusters
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-41588
The text was updated successfully, but these errors were encountered: