Closed Bug 659505 Opened 14 years ago Closed 14 years ago

Redis for SUMO Production

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jsocol, Assigned: oremj)

Details

At some point in the next 6-ish weeks, we're going to need Redis available for SUMO production. We should probably follow the AMO model of having two redis-server processes, one used for cache data that we can flush, and the other for persistent, non-volatile data. Trying to file early before this is a rush.
Similar to bug 659515 we should get data from this into Ganglia when it's ready.
The "AMO model" of doing redis exposed a single point of failure over the weekend that caused issues. Will be discussing things with them this week and then we can consult on this.
It's possible to have slave Redis instances. What was the issue? I'd be interested to listen in on any calls/meetings talking it out.
We need this by the end of June or we're going to be blocked. We don't necessarily need the volatile cache by then--that's controllable by a setting and off by default--but we'll need the persistent one. We have example configs and puppet templates in git, under configs/redis/. If those configs need to be tweaked, let us know.
Any update here?
Assignee: server-ops → jeremy.orem+bugs
Filed bug 665127 to request hardware.
redis is set up on supportredis1.webapp.phx1.mozilla.com 6379 for non-persistent 6380 for persistent I've verified that the we servers can talk to those ports, so everything should be good to go.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.