capture write times to adjust lease timeout #99
Merged
+241
−123
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.
Fixes #83
Fixes #88
Summary of Changes
Currently we "auto-lease" messages for the user, this means that we continuously modify the ackdeadline in an attempt to prevent messages being processed from being re-delivered. This involves setting a recursive timeout which is calculated like so
99th percentile of ack times * 0.9 * random (jitter)
However this doesn't account for any latency from writing to the subscription stream. This PR captures the time it takes to finish writing to a stream and adjusts the lease timeout accordingly.