Closed Bug 875503 Opened 11 years ago Closed 11 years ago

mdn: enable redis

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: groovecoder, Assigned: bburton)

Details

(Whiteboard: [triaged 20130524])

developer1-3 are having connection issues with the RabbitMQ celery broker. We'd like to try using a Redis-based broker instead. Can we make a Redis server available to developer1.dev, developer1.stage, developer1-3, and developer-celery1 nodes?
Assignee: server-ops-webops → bburton
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [triaged 20130524]
We don't currently support Redis as a service that we can guarantee is highly available We have RabbitMQ clusters in each DC that are highly available and we're using for numerous Celery deployments Let's troubleshoot your usage of Rabbit first, with https://bugzilla.mozilla.org/show_bug.cgi?id=877863
We believe we resolved the issue by fixing an incorrect (too low) zeus timeout for the rabbitmq frontend vip.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.