From: Eric Wong <normalperson@yhbt.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>, git@vger.kernel.org
Subject: Re: git-pull from git.git - no remote ref for pu or next?
Date: Tue, 12 Dec 2006 13:26:12 -0800 [thread overview]
Message-ID: <20061212212612.GA22497@localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0612120949230.3535@woody.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
> > And then it mysteriously fixed itself a few minutes later.
> > Is there some sort of publishing failure, or intermittent race condition?
>
> But because the public sites just mirror using rsync, and aren't really
> aware of git repositories etc at that stage, what can happen is that a
> mirroring is on-going when Junio does a push, and then the changes to the
> "refs/" directory might get rsync'ed before the "object/" directory does,
> and you end up with the public sites having references to objects that
> don't even _exist_ on those public sites any more.
>
> And once the mirroring completes, the issue just goes away, which explains
> why it just magically works five minutes later.
If kernel.org isn't using it already, I've found the --delay-updates
option of rsync works reasonably well and can cut down the
race-condition window. It does use more memory and disk space, however.
atomic-rsync (a perl front-end distributed with the rsync source) takes
even more disk space but works across an entire subdirectory all at once
(with 2 renames)
--
prev parent reply other threads:[~2006-12-12 21:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 16:44 git-pull from git.git - no remote ref for pu or next? Randal L. Schwartz
2006-12-12 16:47 ` Randal L. Schwartz
2006-12-12 17:40 ` Johannes Schindelin
2006-12-12 17:42 ` Randal L. Schwartz
2006-12-12 17:56 ` Linus Torvalds
2006-12-12 18:09 ` Johannes Schindelin
2006-12-12 18:23 ` Linus Torvalds
2006-12-12 19:07 ` Nicolas Pitre
2006-12-12 19:13 ` Linus Torvalds
2006-12-12 19:18 ` Jakub Narebski
2006-12-12 18:54 ` Nicolas Pitre
2006-12-12 19:04 ` Johannes Schindelin
2006-12-12 19:15 ` Jakub Narebski
2006-12-12 19:26 ` Nicolas Pitre
2006-12-12 19:32 ` Johannes Schindelin
2006-12-12 19:48 ` Linus Torvalds
2006-12-12 20:04 ` Jakub Narebski
2006-12-12 20:26 ` Johannes Schindelin
2006-12-12 19:50 ` Nicolas Pitre
2006-12-12 18:51 ` Nicolas Pitre
2006-12-12 19:03 ` Linus Torvalds
2006-12-12 21:26 ` Eric Wong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061212212612.GA22497@localdomain \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).