ingester: shortcut fetchWants that have already been satisfied #9891
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does
After #9855 and the assertions in
pollFetchesAndAssertNoRecords
there were some flaky tests (TestConcurrentFetchers/consume_from_end_and_update_immediately
in particular). This happened because some fetch would satisfy the future fetchWants. Future fetchWantes would only end up buffering records and then discarding them at PollFetches.The tests are more obviously flaky if you make consuming records a bit more expensive, for example, but changing the logger with
The fix
This PR shortcuts this, so the tests are less likely to be flaky. Now we can still make a request for a fetchWants that's been satisfied, but it's less likely and there will only be up to
concurrency
of these.Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.