It's not there. Writing it wouldn't be that hard. https://redis.io/topics/sentinel
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Add sentinel profile and role | operations/puppet | production | +53 -0 | |
redis: Add redis::sentinel class | operations/puppet | production | +152 -0 |
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 | |||
Invalid | None | T210580 Write puppet for redis-sentinel |
Event Timeline
Change 476891 had a related patch set uploaded (by Ladsgroup; owner: Ladsgroup):
[operations/puppet@production] [WIP] redis: Add redis::sentinel class
Change 477415 had a related patch set uploaded (by Ladsgroup; owner: Ladsgroup):
[operations/puppet@production] Add sentinel profile and role
I'll note that I ended up puppetizing redis-sentinel for Toolforge use, although it's currently not available as a standalone module: https://gerrit.wikimedia.org/r/c/operations/puppet/+/690528
I 'll close then. This was specifically for the ORES case, T122676, which hasn't happened. @Majavah has been kind enough to contribute puppet code for the toolforge redis-sentinel use case. I think that we have no reason to say that the latter covers the needs of the former right now. The former has been abandoned, which makes me think that Invalid is the valid status for this one. Feel free to reopen though.