Duplicated notifications
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 887
- PR merge metrics
- No merged PRs in 30d
Description
When using
```
queue:
engine: "redis"
redis:
addr: "keydb.gorush.svc.cluster.local:6379"
group: gorush
consumer: gorush
stream_name: gorush
```
And if you deploy in K8s with multiple container, each container will send the same notification. So basically you cannot scale because of this. Happens in latest version as well
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Redis queue configuration shown in the issue and reproduce it using multiple containers in Kubernetes. Trace notification consumption and compare deliveries across containers; done means scaling the deployment no longer sends duplicate notifications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, redis
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100