Last modified: 2014-04-06 09:54:09 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 T65575, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 63575 - Replication has stopped for s1 and s4
Replication has stopped for s1 and s4
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: Unprioritized blocker
: ---
Assigned To: Sean Pringle
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-04-05 16:24 UTC by Tim Landscheidt
Modified: 2014-04-06 09:54 UTC (History)
6 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Tim Landscheidt 2014-04-05 16:24:16 UTC 
Replication lag is now at about 4350 s for s1 and 83440 s for s4 (cf. also http://permalink.gmane.org/gmane.org.wikimedia.labs/2304).
Comment 1 Betacommand 2014-04-05 16:27:44 UTC 
See http://tools.wmflabs.org/betacommand-dev/cgi-bin/replag
Comment 2 Sean Pringle 2014-04-06 09:54:09 UTC 
This has recovered. Some users were running very slow DELETE queries of the form DELETE ... WHERE ... (SELECT ... ) with no limits or batches. This sort of bad practice has been brought up on Labs-l previously, but it seems it will need policing.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links