tpd: one transport heartbeat per timeline slot; uptime from the timeline - #5271
Merged
Merged
Conversation
Three paths report transport heartbeats (CXO reconcile every 30 s, HTTP register, telemetry every 90 s), each an 8-command pipeline, so every live transport cost redis a write every ~20 s. Uptime was count/960, which that rate saturated at 100%. The store now writes at most one heartbeat per 5-minute slot per transport, and a day's uptime is the share of its 288 timeline slots that are set — exact regardless of how many paths report. The online threshold is two slots.
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.
Three paths report transport heartbeats (CXO reconcile every 30 s, HTTP register, telemetry every 90 s), each an 8-command redis pipeline, so every live transport cost a write every ~20 s — most of the HINCRBY/SADD/EXPIRE load on the TPD host. Uptime was count/960, which that rate saturated at 100%.
The store now writes at most one heartbeat per 5-minute slot per transport, and a day's uptime is the share of its 288 timeline slots that are set — exact regardless of how many paths report. Rewards are unaffected (they use visor uptime). The online threshold is now two slots.