-----Original Message----- From: Martijn Faassen [mailto:m.faassen@vet.uu.nl] Sent: Tuesday, November 30, 1999 12:49 PM To: zope@zope.org Subject: [Zope] ZCatalog: No Space Left on Device
Hi there,
Sometimes when I'm ZCatalogging (in Zope 2.0.1) a lot of objects it aborts (after a long time) with 'no space left on device'. This while there is still over a 100 megs of space on the drive. Anyone have any clue what this means?
ZCatalog uses subtransactions, which are temporary miniature 'commits' to the ZODB so that memory doesn't grow beyond physical limits when changing lots and lots of objects in one transaction. When a subtransaction is commited, it allows the ZODB to move those 'sub-commited' objects to a temporary file if memory gets tight. This temporary file is probably filling up your /tmp filesystem. The solution is to set your commit threshold much higher, ie, commit sub-transactions less frequently. -Michel
Michel Pelletier wrote: [snip]
ZCatalog uses subtransactions, which are temporary miniature 'commits' to the ZODB so that memory doesn't grow beyond physical limits when changing lots and lots of objects in one transaction. When a subtransaction is commited, it allows the ZODB to move those 'sub-commited' objects to a temporary file if memory gets tight.
This temporary file is probably filling up your /tmp filesystem. The solution is to set your commit threshold much higher, ie, commit sub-transactions less frequently.
Reading the intent instead of the message I set the subtransaction threshold *lower* (from 1000 to 100) and now it seems to work fine. Thanks! I'll watch the /tmp filesystem too next time this kind of thing happens. Regards, Martijn
participants (2)
-
Martijn Faassen -
Michel Pelletier