Last modified: 2007-07-07 04:54:21 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 10211 - Information about server status and reaction on overload
Information about server status and reaction on overload
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
All All
: High enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-06-10 19:45 UTC by Stefan Bauer
Modified: 2007-07-07 04:54 UTC (History)
2 users (show)

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


Description Stefan Bauer 2007-06-10 19:45:58 UTC
By using the API it is very easy to overload the servers even if you don't want to do anything harmful. By designing an application I accidently created to much load, seen with the database lag shown in watchlist and contributions - I could watch increasing the lag nearly in real time.

There should be added two things:
1. a query for the lag of database servers - give applications a chance to recognize heavy load and to react
2. throttle down the API queries inside the API if the lag exceeds a given value or give an overload error - this is needed if an application has does not examine (1) or want's to harm the servers.

If you need my demo queries, I'll send them per mail but I don't want to present them to the public at the moment.
Comment 1 Rob Church 2007-06-10 23:47:53 UTC
Note the existence of "maxlag" -, which is directed more at people making write queries, but which might also be useful guidance for scripts.

In general, it might be wise to consider throttling API requests, but at the same time, we don't want to make the API useless. An additional help might be directing general queries to a separate query group, which could then be later configured to a distinct set of slave database servers.

Storing certain, more expensive API results in the object cache is something else that might be helpful, or perhaps encouraging clients and shared caches to store results for a short period of time in some cases.
Comment 2 Yuri Astrakhan 2007-07-07 04:54:21 UTC
In r23823, added db server replication lag information in meta=siteinfo.
I will close the bug for now, but if it's not enough, please reopen and provide additional requests.

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