-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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 #124359
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.
Checking if KV has any further insight on what we could do here, or if this might just be a flake. (If there's a fix needed on the SQL side, then feel free to point me in the right direction and move it back to our team.) |
@rafiss I think we've seen a similar issue here: #115067. It seems like setting |
It was not updated to be 0.5s in that commit, it seems to have been It doesn't seem like the setting is relevant for cockroach/pkg/ccl/kvccl/kvfollowerreadsccl/followerreads.go Lines 51 to 55 in 46b6fab
|
Thanks for finding both of those. It looks like the max clock offset is used for global reads: cockroach/pkg/ccl/kvccl/kvfollowerreadsccl/followerreads.go Lines 65 to 72 in a3ddfdd
Does this mean it's just a clock issue, and there's nothing else we can configure in this test that would help? 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 keep helping to track down why we would see the |
ccl/multiregionccl.TestMultiRegionDataDriven failed on release-24.1 @ bf5e0e7cafb7537cecab2f70aafd1b4274172e86:
Parameters:
attempt=1
run=1
shard=2
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-38846
The text was updated successfully, but these errors were encountered: