Last modified: 2006-04-25 05:40:20 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 197 - Use timeout thread killer on searches
Use timeout thread killer on searches
Product: MediaWiki
Classification: Unclassified
Search (Other open bugs)
PC All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2004-08-23 18:52 UTC by Brion Vibber
Modified: 2006-04-25 05:40 UTC (History)
1 user (show)

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


Description Brion Vibber 2004-08-23 18:52:54 UTC
We still sometimes get hit by really slow search queries that take a long time to return. It might be wise to use the thread 
timeout killer script that we have for Asksql on searches as well. If the search doesn't return in 30 seconds, there's a good 
chance the user won't still be around to pick it up anyway.
Comment 1 Brion Vibber 2004-11-22 09:29:50 UTC
We've got an external thread-killer daemon (servmon) which currently serves this need on Wikimedia. Do we need 
something more integrated? I don't really like the way the old asksql killer worked (shell-out to run PHP), it wasn't 
necessarily clean or portable itself.
Comment 2 Jamesday 2004-11-22 12:20:16 UTC
MySQL AB has plans in this area as well, perhaps for their version 5 - ETA 9-12
months or so for production release.
Comment 3 Brion Vibber 2006-04-25 05:40:20 UTC
No longer relevant.

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