-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Batch GRV Rate Limit Exceeded is not always thrown #11500
Comments
ok, I created a reasonable reproduction at: https://github.com/FoundationDB/fdb-record-layer/pull/2823/files |
I think we have stampled across this issue in simulation. We have a very basic RL's fork in Rust that we can simulate as an external workload. We found this morning a specific seed (
Our testfile looks like this:
Let me know if we can help 😄 |
The tests noted in FoundationDB/fdb-record-layer#2813 will occasionally run forever due to this code:
https://github.com/FoundationDB/fdb-record-layer/blob/200ac05041a1af712f621a27b4c5c37f9eab001c/fdb-record-layer-core/src/main/java/com/apple/foundationdb/record/provider/foundationdb/storestate/FDBRecordStoreStateCacheEntry.java#L97-L100
Where it is combining two futures.
The first one:
recordStore.loadRecordStoreStateAsync
is doing a regular read.The second one is doing a snapshot get of
SystemKeyspace.METADATA_VERSION_KEY
.The first future fails with
Batch GRV request rate limit exceeded
(code 1051).The second future never completes.
I have tried to reproduce this in a more isolated environment, but it is proving tricky to get it to reliably start failing with
Batch GRV request rate limit exceeded
.The text was updated successfully, but these errors were encountered: