Izak Burger wrote:
Before I dive into the code and attempt to find the problem, I thought
I'd post first, partly to report the problem, but at the same time to
find out if anyone has seen this and if perhaps a fix is already available.
Never experienced this myself, what storage(s) are you
Jim Fulton wrote:
I haven't seen this and, looking at the code on the trunk, I see no
reason why many savepoint temporary storages or ZEO transaction
buffers would be kept open. Savepoint temporary storages are closed
after use
I wonder if Izak inadvertently has lots of savepoints
On Thu, Jun 25, 2009 at 4:46 AM, Izak Burgeri...@upfrontsystems.co.za wrote:
Hi all,
This is a zope issue that I think is probably zodb related. I've been
seeing this behaviour for a couple of years now. When I inspect
/proc/PID/fd (on a linux machine, this lists the open file descriptors
Benji York wrote:
Have you looked at the contents of the files? Once you have an idea of
what is being written you might be able to determine what is doing the
writing.
The big 6.3GB one contains pickles. Lots and lots of pickles.
I suspect we're simply dealing with a process that creates a
Izak Burger wrote:
I suspect we're simply dealing with a process that creates a LOT of
savepoints before finally committing. The developer of the application
is out at the moment, when he gets back from his lunch-break/touch-rugby
game I shall ask him about this.
The developer confirmed
On Thu, Jun 25, 2009 at 7:19 AM, Izak Burgeri...@upfrontsystems.co.za wrote:
Benji York wrote:
Have you looked at the contents of the files? Once you have an idea of
what is being written you might be able to determine what is doing the
writing.
The big 6.3GB one contains pickles. Lots and
On Jun 25, 2009, at 6:56 AM, Chris Withers wrote:
Jim Fulton wrote:
I haven't seen this and, looking at the code on the trunk, I see
no reason why many savepoint temporary storages or ZEO
transaction buffers would be kept open. Savepoint temporary
storages are closed after use
I
