According to redis-sentinel guide:
Fundamental things to know about Sentinel before deploying
You need at least three Sentinel instances for a robust deployment.Thus having a new node for oresrdb is needed before deploying sentinel to prod.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T181538 ORES overload incident, 2017-11-28 | |||
| Resolved | Ladsgroup | T181632 Celery manager implodes horribly if Redis goes down | |||
| Resolved | Ladsgroup | T181559 Investigate redis-cluster or other techniques for making Redis not a single point of failure. | |||
| Declined | None | T122676 Implement sentinel for ORES production Redis | |||
| Declined | None | T210582 New node request: oresrdb[12]003 |
Event Timeline
Comment Actions
I think we should pause this request until the choices that generated this ticket have been properly discussed with the SRE team.
Comment Actions
It's been a year already with no move on this one. I 'll mark as declined (that and parent task). We can always revisit and reopen.
Comment Actions
There are no oresrdb nodes at all anymore. ORES redis has been moved to the redis::misc cluster. This is probably no longer relevant. I 'll remove the vm-requests tag, feel free to readd.