| 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 | |||
| Resolved | Halfak | T167149 Test if ORES celery can use the unix socket | |||
| Resolved | Ladsgroup | T196889 Investigate what is creating Redis transactions and whether it can be fixed | |||
| Declined | None | T210577 Build a test setup for redis sentinel in cloud VPS | |||
| Resolved | Ladsgroup | T210579 Add support for redis-sentinel in score cache | |||
| Invalid | None | T210580 Write puppet for redis-sentinel | |||
| Declined | None | T210582 New node request: oresrdb[12]003 | |||
| Declined | None | T210605 Run a test failover in labs before migrating prod to sentinel |
Event Timeline
Comment Actions
Hi @Ladsgroup can you please elaborate on why you decided to go with sentinel, and who in the SRE teams was involved in this choice?
As it stands, this ticket gives me zero information on your line of reasoning and on your specific needs, so that I can give you an informed suggestion, on what could work, and on what the SRE team is comfortable working with.
Thanks!