Add Redis backend guide for HA metrics aggregation#113
Open
noalimoy wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
the
size/L
noalimoy
force-pushed
the
config/redis-ha-metrics-aggregation
branch
from
bf57680 to
0c0f743
Compare
…A metrics aggregation Signed-off-by: noalimoy <nlimoy@redhat.com>
noalimoy
force-pushed
the
config/redis-ha-metrics-aggregation
branch
from
0c0f743 to
0e1396d
Compare
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
2 participants
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 does this PR do?
Add
config/redis/README.md— a deployment, configuration, and verification guide for the Redis-backed DataStore, enabling HA metrics aggregation across multiple IPP replicas.Why is this change needed?
With a single replica, the in-memory DataStore holds the complete picture. Under HA (multiple replicas), each sees only a subset of requests — Scorers make routing decisions on partial data (#79, #85).
This guide documents the Redis backend approach — per-replica keys with TTL, heartbeat/refresh goroutines, and zero network calls on the hot path.
How was this tested?
Documentation-only change. Verified that Redis YAML manifests are valid, code references (
AttributeMap,InflightRequestsCount,Get()/Put()) match merged code onmain, and Helm values align with existingvalues.yamlconventions.Checklist
git commit -s) per DCOmake test)make lint)Related Issues
Refs: #79
Refs: #85