On Mon, Oct 29, 2012 at 10:46 PM, Philip Martin <philip.mar...@wandisco.com>wrote:
> Philip Martin <philip.mar...@wandisco.com> writes: > > > Philip Martin <philip.mar...@wandisco.com> writes: > > > >> I can't see any order in which we can do attach/create that doesn't have > >> a similar race. I think the best solution is a short loop trying > >> attach-create a few times before giving up. > > > > I've committed a loop in r1403463. That doesn't fix the race but it is > > now very unlikely to fail. > The creation code is protected by a repo-global lock/unlock pair. So, in theory, there should be no race condition. > I've just observed the same failure with the looping code. I'm not sure > what is wrong. I suppose there is a window during the creation process > where the file exists, so the create fails, but the memory is not yet > ready, so the attach also fails. If one process is in this state > another process might loop around 10 times and have both create and > attach fail. Perhaps a short and/or random delay would help? > It's on my TODO list to identify the root cause of this issue. -- Stefan^2. -- Certified & Supported Apache Subversion Downloads: * http://www.wandisco.com/subversion/download *
