Last modified: 2005-12-10 18:01:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 951 - Watchlist fails to update
Watchlist fails to update
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 2637 (view as bug list)
Depends on:
Blocks: db-repl-track 372
  Show dependency treegraph
 
Reported: 2004-11-27 19:17 UTC by Leah
Modified: 2005-12-10 18:01 UTC (History)
1 user (show)

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


Attachments

Description Leah 2004-11-27 19:17:24 UTC
Special:Watchlist appears to have stopped working at about 11:00 CST.
Comment 1 JeLuF 2004-11-27 19:36:29 UTC
DB server lags, removed from replication
Comment 2 Leah 2004-12-09 19:27:04 UTC
Watchlists have stopped again at about noon.
Comment 3 River Tarnell 2004-12-09 19:33:40 UTC
Will catch up shortly.
Comment 4 Jamesday 2004-12-09 21:02:37 UTC
For background, there are three main causes of this:

1. Too much load on the slave, so it can't keep up with replication while it
handles queries. In this situation, we adjust load by adjusting the amount of
search we turn off. If they get significantly behind, we turn off search for
some of the big wikis using that slave so it can catch up more quickly.

2. An operating system version-related issue on the slave Bacon, which causes it
to stop replicating. We can't risk losing Bacon at present so we can't try
different operating system versions yet. Becuase we get fast reports of this
problem from en, we have this machine set to serve en and Zh wikipedias. The
rest are normally unaffected by this issue with the current setup, though in 
the past any could be affected. The split is mainly for performance reasons - we
just had to choose which wikis got the one with the problem.

3. Any other operation which causes replication to stop. There are a wide range
of possibilities. This is less commmon than 1 or 2.

For 1 and 2, on 14 October 2004 we ordered two more database slaves to add to
the two we have. They are being set up now, after delays at both the vendor due
to a compatibility issue and with our install person being unavailable. The new
ones have a different operating system version from Bacon and will confirm
whether that resolves the problem Bacon is having, as well as giving us enough
excess capacity to risk losing Bacon for a while if there is a problem while
switching it to that version.
Comment 5 Jamesday 2005-01-13 22:32:08 UTC
The Bacon problem is still around but has been worked around with a modification
to servmon which automtically corrects the problem. It's seen less often on the
new system with the later operating system version, only once so far.

The two new database servers have reduced the general lag problems. Search is
now on full time at full rate. Some MediaWiki 1.4 issues (changed queries) which
can cause lag are still being identified and dealt with - either with querybane
rules or programming chances in MediaWiki.

Two comon causes of significant lag have been removed: special page updating is
now done on a different, not in service, server and copied in without
significant lag. Searchindex updating is also done while slaves are offline and
no longer causes lag.
Comment 6 Brion Vibber 2005-12-10 01:14:48 UTC
Guess this is no longer an issue. ;)
Comment 7 Brion Vibber 2005-12-10 01:17:28 UTC
*** Bug 2637 has been marked as a duplicate of this bug. ***

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


Navigation
Links