Use copy on write collection for tracking stored files #1708
+5
−7
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.
Goal
Tracing of the delivery layer from flaky tests indicates that the payload store is erroneously telling the scheduling service that 0 payloads are persisted on disk. I'm suspicious that this might be due to the implementation of
storedFiles
ingetPayloadByPriority
as it uses aConcurrentSkipListSet
, whose operations are async. I'd hypothesise that in our tests and also in prod this can result in a race condition where payloads aren't delivered by the scheduling service on the first attempt (although subsequent attempts do result in delivery).Altering the implementation to use
CopyOnWriteArraySet
should fix this if the theory is correct.