Last modified: 2011-11-17 00:33:47 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 T33388, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 31388 - mysql caching is consuming more disk space on 1.18 wikis due to change in parser cache keys
mysql caching is consuming more disk space on 1.18 wikis due to change in par...
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Tim Starling
:
Depends on:
Blocks: 29876
  Show dependency treegraph
 
Reported: 2011-10-05 18:38 UTC by Mark A. Hershberger
Modified: 2011-11-17 00:33 UTC (History)
5 users (show)

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


Attachments

Description Mark A. Hershberger 2011-10-05 18:38:15 UTC
We're running out of disk space and this needs to be fixed in the next few hours.  See http://ganglia.wikimedia.org/graph.php?c=MySQL&h=db40.pmtpa.wmnet&v=406.493&m=disk_free&r=day&z=medium&jr=&js=&st=1317836378&vl=GB&ti=Disk%20Space%20Available

More details may be added, but Roan is currently running a query to see how much space can be cleared up by deleting space used by an old iOS hack.
Comment 1 Rob Lanphier 2011-10-05 21:04:39 UTC
Domas has a short term workaround, which involves periodically truncating one of the 256 tables in the parser cache.  This has had a negative effect on our hit rate:
http://noc.wikimedia.org/cgi-bin/pcache-hit-rate.py?period=8d
(note: yellow is bad)

...but, as you can see from the disk utilization graph above, we're not chewing through disk anymore.  I'm assigning to Tim since he's responsible for the long-term fix, but Domas has fixed the most urgent problem.
Comment 2 Domas Mituzas 2011-10-05 21:38:54 UTC
it isn't "periodically truncating one", it is "truncating all over extended period" - as old data will not be referenced anyway.
Comment 3 Tim Starling 2011-10-05 22:22:25 UTC
Turning down priority/severity due to temporary fix.
Comment 4 Rob Lanphier 2011-11-17 00:33:47 UTC
The immediate crisis is averted.  Will create separate bug to make sure we've got regular purging going on.

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


Navigation
Links