This is useful for tewmproxy.
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 | |||
| Resolved | Halfak | T167149 Test if ORES celery can use the unix socket |
Event Timeline
Comment Actions
Nope. It should be able to, but this is a blocker: https://github.com/andymccurdy/redis-py/pull/839
See also https://github.com/celery/celery/issues/2903
For some reason, redis-py/celery communities aren't dealing with this. So, here we are.
Comment Actions
OK, that's fine. We can just fallback to using the TCP connection. I 'll https://gerrit.wikimedia.org/r/350421 respectively. Even the above issue ever get's fixed we can migrate to unix sockets then.