Last modified: 2014-10-24 14:20:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T59583, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57583 - Make deployment prep have continuous replication lag
Make deployment prep have continuous replication lag
Status: NEW
Product: Wikimedia Labs
Classification: Unclassified
deployment-prep (beta) (Other open bugs)
unspecified
All All
: Lowest enhancement
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 60058
Blocks: db-repl-track 51494
  Show dependency treegraph
 
Reported: 2013-11-26 11:05 UTC by Siebrand Mazeland
Modified: 2014-10-24 14:20 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Siebrand Mazeland 2013-11-26 11:05:00 UTC
Replication lag in production can cause weird issues that are very hard to debug. Now that we run automated integration tests, always having a replication lag in our deployment environment may surface issues that developers usually are not aware of, and help us create better code.
Comment 1 Sam Reed (reedy) 2014-04-28 16:02:27 UTC
(In reply to Siebrand Mazeland from comment #0)
> Replication lag in production can cause weird issues that are very hard to
> debug. Now that we run automated integration tests, always having a
> replication lag in our deployment environment may surface issues that
> developers usually are not aware of, and help us create better code.

From bug 60058

(In reply to Erik Bernhardson from comment #1)
> setting the lag is fairly trivial,  percona makes a tool for it called
> pt-slave-delay.


That, and we need to have slaves setup first...
Comment 2 Antoine "hashar" Musso (WMF) 2014-10-24 14:20:10 UTC
Marking to lowest priority since nobody is sponsoring this for now.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links