From: Junio C Hamano <gitster@pobox.com>
Date: Sun, 03 May 2015 02:12:06 GMT
Subject: Re: [PATCH 0/2] Retry attempts to acquire the packed-refs lock
Message-ID: <xmqqtwvuwgsp.fsf@gitster.dls.corp.google.com>
In-Reply-To: <1430491977-25817-1-git-send-email-mhagger@alum.mit.edu>

Michael Haggerty <mhagger@alum.mit.edu> writes:

> At GitHub we were seeing occasional lock contention over packed-refs.
> It wasn't very common, but when you have as much git traffic as we
> have, anything that *can* happen *will* happen.
>
> The problem is that Git only tries to acquire locks a single time. If
> that attempt fails, the whole process fails. So, for example, if two
> processes are trying to delete two different references, one of them
> can fail due to inability to acquire the packed-refs lock, even though
> it could have succeeded if it had just waited a moment.

Yeah, try and abort may be perfectly fine for Git used interactively
by humans, but is totally unsuitable for the server side.  Thanks
for looking into this.