Page MenuHomePhabricator

Check multi-datacenter compatibility with GettingStarted's use of Redis
Closed, ResolvedPublic


It's used for keeping an auto-updated list of relevant articles in particular categories.

Event Timeline

Mattflaschen-WMF raised the priority of this task from to Medium.
Mattflaschen-WMF updated the task description. (Show Details)
Mattflaschen-WMF added subscribers: mark, Joe, Krenair and 6 others.

Looks like RedisCategorySync::getRedis() can just take a master/slave flag. All the writes happen on POST anyway, and those would go to the master server in the main DC. The redis slave would be used for the srandommember call.

Looking at the current production config, I've found the list of session redis servers that GetingStarted picks the first from. That list doesn't indicate if any of these servers are slaves, though. Is there any way for me to know? Or is that information buried in ops' production puppet control panels?

Change 201948 had a related patch set uploaded (by Gilles):
Add ability to connect to a master or slave Redis instance

The mc1001-1016 servers have no slaves in eqiad. The only slaves they ever have are in the other DC.

I'd assume for eqiad, the "slave" would just be the master. Not sure if this is in puppet yet.

Not seeing any hierdata in puppet yet.

Change 201948 merged by jenkins-bot:
Add ability to connect to a master or slave Redis instance

Gilles removed Gilles as the assignee of this task.Jun 2 2015, 8:25 AM
Gilles removed a project: Patch-For-Review.
Gilles set Security to None.
aaron claimed this task.