Closed
Bug 934627
Opened 11 years ago
Closed 11 years ago
Migrate signing to a webops-supported redis instance
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dustin, Assigned: dustin)
Details
This currently uses redis, and we want to kill redis as part of bug 846332.
Assignee | ||
Updated•11 years ago
|
Assignee: relops → dustin
Assignee | ||
Updated•11 years ago
|
Summary: Migrate signing to a memcached backend → Migrate signing to a webops-supported redis instance
Comment 1•11 years ago
|
||
Dustin - a couple of concerns raised this morning at the buildduty meeting: * will we be getting our own private namespace on the shared redis instance? * we been burned by redis outages on the existing releng system a few times in the past month - how soon can we switch over to the shared redis instance? Who/what is it gated on and how can we help?
Assignee | ||
Comment 2•11 years ago
|
||
The namespace configuration will be exactly as it is on redis01, meaning that buildapi and signing share a namespace. That's bad, and the reason for bug 945751. Probably the best way to help is to implement bug 945751, but barring that, webops will be working on setting up redis soon for buildapi, anyway.
Assignee | ||
Comment 3•11 years ago
|
||
WONTFIX in favor of bug 945751
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Resolution: FIXED → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•