Test concurrent cloning/slicing of IndexInputs #51032
Merged
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.
We test the behaviour of an
IndexInput
usingrandomReadAndSlice()
whichuses a wide varity of different access methods to read the data. Lucene
sometimes calls
clone()
andslice()
concurrently, although it does ensurethat there are no concurrent readers while these are being called. Today we do
not verify that our
IndexInput
s behave correctly under this kind ofconcurrent access.
This commit extracts
randomReadAndSlice()
into a separate test harness formore general consumption and adds support for concurrent cloning and slicing.