-
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
ccl/multiregionccl: TestMultiRegionDataDriven failed [can't serve follower read; closed timestamp too low by: 10ms] #125755
Comments
The relevant part of the the trace is here, which says a follower read couldn't be used since the closed timestamp was too low:
Right before this, the test verifies that the correct closed timestamp policy is being used.
I dug in a bit further into the KV code where the cockroach/pkg/kv/kvserver/replica_follower_read.go Lines 106 to 121 in e9a6d3d
I'm not familiar with this code, so I'm not sure how this relates to Hoping the KV team can help to track down why we would see the This previously came up in #124359. In that issue, the |
@rafiss this test seems to be failing because the closed timestamp hasn't propagated to the follower so it can't serve the read. Looks like this flaked; we see a fair few side transport connections dropped in the logs:
I'll close this out as an infra flake. In general, if you see such symptoms where the closed timestamp is lagging (esp on EngFlow, where tests seem to run into overload issues), feel free to close them out as infra flakes; they're annoying but benign. |
ccl/multiregionccl.TestMultiRegionDataDriven failed on release-24.1 @ 35c3e0c133c56c91399e730f49bc488cf6dd4c11:
Parameters:
attempt=1
run=8
shard=2
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-39595
The text was updated successfully, but these errors were encountered: