Page MenuHomePhabricator

implement master-slave DB for beta labs
Closed, ResolvedPublic

Description

The beta cluster is intended to be "close" to production for testing purposes, but it does not use a master-slave DB configuration. This means that some cache and database bugs aren't caught in testing on beta labs, e.g. bug 59884.

It would be useful if beta labs had a similar master-slave DB setup, especially if we introduced significant lag time in slave updates. Easier said than done :-)


Version: unspecified
Severity: enhancement

Details

Reference
bz60058

Event Timeline

bzimport raised the priority of this task from to Normal.Nov 22 2014, 2:54 AM
bzimport set Reference to bz60058.
bzimport added a subscriber: Unknown Object (MLST).

setting the lag is fairly trivial, percona makes a tool for it called pt-slave-delay.

Reedy added a comment.Apr 28 2014, 4:03 PM

(In reply to Erik Bernhardson from comment #1)

setting the lag is fairly trivial, percona makes a tool for it called
pt-slave-delay.

(In reply to spage from comment #0)

It would be useful if beta labs had a similar master-slave DB setup,
especially if we introduced significant lag time in slave updates. Easier
said than done :-)

Bug 57583 requests the lags specifically...

Reedy added a comment.Apr 28 2014, 4:43 PM

Currently doing this!

Reedy added a comment.Apr 28 2014, 8:23 PM

We has a slave!

Thank you Sam!