feat: improve redis dedupe failover handling [poc]#4485
Draft
turip wants to merge 1 commit into
Draft
Conversation
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
Summary
sink.dedupeWriteTimeoutaround the post-persist Redis dedupe write path.3.Flow-level rationale
The sink flow persists a batch to storage, stores Kafka offsets, and then writes dedupe keys to Redis. At that point the worker is in the consistency-sensitive part of the flow: if Redis dedupe writes fail, future replays can accept duplicate events even though the batch was already persisted.
Before this change, the dedupe write retried with implicit retry defaults. During Redis primary failover, go-redis can remove only the checked-out bad connection while other stale connections remain in the pool. A fixed retry count can therefore be consumed by stale pooled connections before a fresh connection dials and resolves the writable endpoint again.
This change keeps the read-side uniqueness checks fail-fast, but makes the post-persist dedupe write path more resilient. The retry loop is bounded by
dedupeWriteTimeout, and reconnect-worthy write errors now swap the Redis client so the next retry starts with a fresh pool and fresh endpoint resolution.Validation
go test ./openmeter/dedupe/redisdedupe ./app/config ./pkg/redis ./openmeter/sink ./app/common