Last modified: 2014-08-26 20:04:52 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 T71776, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69776 - dewiki / wikidatawiki replication (s5) has stopped on labsdb1001/labsdb1002
dewiki / wikidatawiki replication (s5) has stopped on labsdb1001/labsdb1002
Status: RESOLVED WORKSFORME
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: Unprioritized blocker
: ---
Assigned To: Marc A. Pelletier
: ops
Depends on:
Blocks: labs-replication
  Show dependency treegraph
 
Reported: 2014-08-20 09:15 UTC by merl
Modified: 2014-08-26 20:04 UTC (History)
4 users (show)

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


Attachments

Description merl 2014-08-20 09:15:46 UTC
No new data since 20140819190634 on dewiki and wikidatawiki databases available.
Comment 1 Alex Monk 2014-08-23 18:20:54 UTC
Is this still broken? I can see that new revisions are going in to the revision table when I `sql dewiki` (or directly to the mentioned hosts with `mysql -h labsdb<#>.eqiad.wmnet -u <my username> dewiki_p -p`) and run "select max(rev_timestamp) from revision;"
Comment 2 Marc A. Pelletier 2014-08-26 14:33:02 UTC
There is no current issue with either dewiki and wikidatawiki, and revisions are coming in with no significant lag (subsecond).

Occasionally, a long-running query that locks tables can delay replication for several hours before it is found and killed, perhaps that is what happened here.
Comment 3 merl 2014-08-26 20:04:52 UTC
The replication had been stopped some minutes after a wikidatawiki db schema change was executed on wmf cluster to enable wikidata as langlinks repository on wikidata pages. The problem seems to be fixed since the night from Thursday to Friday morning to days laters

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


Navigation
Links