> -----Original Message-----
> From: Hyrum K. Wright [mailto:hyrum_wright_at_mail.utexas.edu]
> Sent: Thursday, March 05, 2009 8:01 PM
> To: Lieven Govaerts
> Cc: dev_at_subversion.tigris.org
> Subject: Re: 1.5 and 1.6 svnsync errors over serf
>
> On Mar 5, 2009, at 12:23 PM, Lieven Govaerts wrote:
>
> > Hyrum K. Wright wrote:
> >> On Mar 5, 2009, at 11:35 AM, Hyrum K. Wright wrote:
> >>
> >>> While doing a svnsync of our repo (actually, two of them) to my
> >>> local
> >>> disk, I ran into the following problem:
> >>>
> >>> Committed revision 7446.
> >>> Copied properties for revision 7446.
> >>> Transmitting file data ....
> >>> Committed revision 7447.
> >>> Copied properties for revision 7447.
> >>> Transmitting file data .subversion/libsvn_ra_serf/replay.c:824:
> >>> (apr_err=24)
> >>> svnsync: Error retrieving replay REPORT (24): Too many open files
> >>> Abort trap
> >>> dhcp-198-227:test Hyrum$
> >>>
> >>> dhcp-198-227:test Hyrum$ ulimit -aS
> >>> core file size (blocks, -c) 0
> >>> data seg size (kbytes, -d) 6144
> >>> file size (blocks, -f) unlimited
> >>> max locked memory (kbytes, -l) unlimited
> >>> max memory size (kbytes, -m) unlimited
> >>> open files (-n) 256
> >>> pipe size (512 bytes, -p) 1
> >>> stack size (kbytes, -s) 8192
> >>> cpu time (seconds, -t) unlimited
> >>> max user processes (-u) 266
> >>> virtual memory (kbytes, -v) unlimited
> >>> dhcp-198-227:test Hyrum$
> >>>
> >>> I would think that 256 files would be plenty for a sync, and it
> >>> worked
> >>> just fine when I restarted the sync after the failure. Are we
> >>> leaving
> >>> file handles open somewhere in serf?
> >>
> >> Further testing indicates that this happens much more often using
> 1.6
> >> than 1.5 (both using serf).
> >>
> > Does the same thing happen with ra_neon? I don't really see any serf
> > specific file-opening happening.
>
> I switched over to ra_neon, and haven't yet seen these errors, so I
> think it's specific to ra_serf.
Hi,
Can you check if the patch I posted on
http://paste.lisp.org/display/76546
resolves this issue for you?
It creates a per revision pool which is then passed to the revision start
and finished handlers. This should clear the pools used for the commit
editor drive.
Bert
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1274360
Received on 2009-03-06 00:34:56 CET