Re: [Mediawiki-l] objectcache table problem

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Gilmer wrote: First, make sure the disk isn't full! Since the cache table is frequently written to it's more likely to show the error even if you have a more fundamental problem. If you're using InnoDB tables, it's also possible that you have a problem with full undo buffers or something weird which results in these 'full' errors. Check google on debugging this... SHOW INNODB STATUS may help diagnose. If your objectcache table really is getting very large, you might want to see what's in it... SELECT keyname, exptime, LENGTH(value) FROM objectcache LIMIT 100; etc Mostly you should see 'messages', 'messages-status', and various parsercache entries: +------------------------------------------+---------------------+-----+ | keyname | exptime |len | +------------------------------------------+---------------------+-----+ | trunkwiki:messages | 2006-12-13 22:11:03 |35089| | trunkwiki:messages-status | 2006-12-12 22:12:03 | 16| | trunkwiki:pcache:idhash:1-0!1!0!!en!2 | 2006-12-13 08:24:13 | 760| | trunkwiki:pcache:idhash:1543-0!1!0!!en!2 | 2006-12-13 04:02:57 | 333| | trunkwiki:pcache:idhash:1553-0!1!0!!en!2 | 2006-12-14 00:07:01 | 320| | trunkwiki:pcache:idhash:1554-0!1!0!!en!2 | 2006-12-14 00:07:10 | 318| | trunkwiki:pcache:idhash:1555-0!1!0!!en!2 | 2006-12-14 00:09:14 | 318| | trunkwiki:pcache:idhash:1556-0!1!0!!en!2 | 2006-12-14 00:09:22 | 320| +------------------------------------------+---------------------+-----+ Do you really have bajillions of legitimate entries? For instance if you're rendering millions of pages, maybe you do have lots of parsercache entries. In this case you might also double-check that you don't have a problem with filesize limits in MySQL... Also consider using memcached for the caches, or disabling the parser cache if you have a specialized use where it's not legitimate. - -- brion vibber (brion @ pobox.com)