Re: svn hung at end of commit operation

Garrett Rooney wrote:
> On 3/22/06, Julian Foad <julianfoad@btopenworld.com> wrote:
>
>>Committing to the Subversion repository just now using Subversion trunk r18992,
>>I got:
>>
>>
>>>~/src/subversion> svn ci -F p && rm p
>>>Sending subversion/include/svn_xml.h
>>>Sending subversion/libsvn_client/prop_commands.c
>>>Sending subversion/libsvn_subr/xml.c
>>>Transmitting file data ...
>
>
> I've seen svn.collab.net seem a bit sluggish at the end of commits
> lately, like the post-commit hooks were taking longer than you'd
> expect them to. Never had it totally hang though, that's pretty
> weird. Was this a one time thing, or was it reproducable?

Here's the post-commit hook in use on svn.collab.net (for all repositories):

---------------------------------------------------------------------
#!/bin/sh

LANG=en_US; export LANG

REPOS=${1}
REV=${2}

# Send a commit mail.
if [ -f ${REPOS}/POST-COMMIT-EMAIL ]; then
    /usr/local/svn/hook-scripts/mailer.py commit "${REPOS}" "${REV}" &
fi

# See http://cia.navi.cx/doc/how-cia-works for what this is about:
if [ -f ${REPOS}/POST-COMMIT-CIABOT ]; then
    /usr/local/svn/hook-scripts/ciabot_svn.py ${REPOS} ${REV} "svn" &
fi

# Run the ViewVC commits database indexer.
if [ -f ${REPOS}/POST-COMMIT-VIEWVC-DB ]; then
    /usr/local/viewvc-1.0-dev/bin/svndbadmin rebuild ${REPOS} ${REV} &
fi
---------------------------------------------------------------------

As you can see, all things are backgrounded. But that does mean there are
three more processes all asking the repository about commit details for the
newly committed revision at the same time. svndbadmin is a new addition
post-migration, but still -- a difference of many *minutes* in post-commit
because of a backgrounded task? That seems really unlikely.

Any ideas?

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand