Bound DocOps bulk operations with a timeout on the aggregate block() - #56
Open
ShivamPaliwal1 wants to merge 1 commit into
Open
Bound DocOps bulk operations with a timeout on the aggregate block()#56ShivamPaliwal1 wants to merge 1 commit into
ShivamPaliwal1 wants to merge 1 commit into
Conversation
Per-op timeouts on insert/upsert/get/delete/replace/touch only guarantee a single request terminates; if the shared reactor scheduler wedges under heavy backpressure (e.g. concurrent disk-full workloads), that signal can fail to reach the blocked caller and .block() hangs the JVM indefinitely. Adding an explicit .timeout() on the aggregate collectList() gives each bulk call its own backstop instead of relying solely on an external stall-watchdog to kill the process.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Per-op timeouts on insert/upsert/get/delete/replace/touch only guarantee a single request terminates; if the shared reactor scheduler wedges under heavy backpressure (e.g. concurrent disk-full workloads), that signal can fail to reach the blocked caller and .block() hangs the JVM indefinitely. Adding an explicit .timeout() on the aggregate collectList() gives each bulk call its own backstop instead of relying solely on an external stall-watchdog to kill the process.