-
Notifications
You must be signed in to change notification settings - Fork 104
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
Lucene tests sometimes stall until they timeout #2813
Comments
ScottDugas
added a commit
to ScottDugas/fdb-record-layer
that referenced
this issue
Jul 10, 2024
…t.concurrentStoreTest Due to FoundationDB#2813 this test can, occasionally, run forever, so add a timeout so that it doesn't.
ScottDugas
added a commit
to ScottDugas/fdb-record-layer
that referenced
this issue
Jul 12, 2024
Loading the metadata version key does not seem to throw Batch GRV rate limit exceeded, while other operations on the same transaciton do. Instead it stalls forever, and the tests end up timing out at the junit level. This change introduces a new combine that will fail when the loading the record store state fails, instead of waiting forever for the metadata version to be loaded.
I believe this is caused by apple/foundationdb#11500 although I'm having trouble creating a valuable reproduction that doesn't involve all of record layer. |
ScottDugas
added a commit
that referenced
this issue
Jul 16, 2024
Fixes #2813: Fail fast when Batch GRV Rate Limit Exceeded
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Specifically some people have noticed that
LuceneIndexTest.fullDeleteHelper
times out after 5 minutes rather than completing, but it's normal runtime is less than 500ms.Similarly the newly added
LuceneIndexMaintenanceTest.concurrentStoreTest
can experience a similar issue.The text was updated successfully, but these errors were encountered: