Add dedupe logic for heartbeat timer creation #962
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.
After moving timer deletion to a background job, it is highly likely to
process timers multiple times. Heartbeat timer processing is made
idempotent by keeping track of the timeout visibility within
mutable state whenever a new timer is created. And we only clear
the timer flag if the last timeout visibility is less than or equal to
visibility timestamp of the timer task.