Last modified: 2014-09-07 19:19:24 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 T72485, 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 70485 - Page inaccessible for ten minutes after edit due to PoolCounter pool-timeout
Page inaccessible for ten minutes after edit due to PoolCounter pool-timeout
Status: NEW
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
wmf-deployment
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: performance
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-09-06 10:18 UTC by Nemo
Modified: 2014-09-07 19:19 UTC (History)
3 users (show)

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

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

Description Nemo 2014-09-06 10:18:27 UTC 
After these three edits, I was unable to access the page and its subpages for 10, perhaps 20 minutes: <https://meta.wikimedia.org/w/index.php?title=Letter_to_Wikimedia_Foundation:_Superprotect_and_Media_Viewer&offset=20140905103524&limit=3&action=history>
The pages took a while to load, then they displayed either a pool-timeout error or an error 504.

Some FuzzyBot edits were triggered by the edits linked above:
* https://meta.wikimedia.org/w/index.php?title=Special:Contributions/FuzzyBot&dir=prev&offset=20140905094952&limit=21&target=FuzzyBot
* https://meta.wikimedia.org/w/index.php?title=Special:Contributions/FuzzyBot&offset=20140905095524&limit=15&target=FuzzyBot

Example from poolcounter.log:

legoktm> metawiki: Pool key 'metawiki:pcache:idhash:5415286-0!*!0!!it!*!*:revid:9761977' (ArticleView): Timeout waiting for the lock
legoktm> at 2014-09-05 09:53:03

No obvious changes in configuration or log patterns recently.

It's not the first time it happens to me and I'm not sure whether it's expected or not (I can understand the operation I made was heavier than a normal edit), but filing for reference.
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