Enforce persistence context timeout in application layer: Part 3 #3631
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 changed?
Enforce persistence context timeout in shard context, execution context and execution cache
Context.Background() is used in unit tests if the test is not testing timeout case.
Why?
#3519
How did you test it?
Integration test.
Potential risks
May result in more persistence context timeout, rangeID change more frequently and more shard movement when persistence latency is high.