From: Andreas Dilger <adilger@clusterfs.com>
To: Larry McVoy <lm@bitmover.com>
Cc: bitkeeper-announce@bitmover.com, linux-kernel@vger.kernel.org
Subject: Re: bkbits.net downtime
Date: Fri, 31 Jan 2003 14:50:18 -0700 [thread overview]
Message-ID: <20030131145018.N3904@schatzie.adilger.int> (raw)
In-Reply-To: <200301312114.h0VLEmC11997@work.bitmover.com>; from lm@bitmover.com on Fri, Jan 31, 2003 at 01:14:48PM -0800
On Jan 31, 2003 13:14 -0800, Larry McVoy wrote:
> Our T1 supplier, Global Crossing, is repairing a router at midnight
> Saturday PST. Expected downtime is 3 hours but you never know. If
> it turns out that they screw things up, we'll physically move bkbits.net
> to a different location Sunday or Monday.
Actually, with BK it should be possible to have read only clones on
multiple servers, should it not? Not that I'm saying BK should foot
the bill to do that, but having read-only clones of the primary kernel
trees would avoid most downtime.
I suppose it would be difficult for two servers to do a merge with
conflicts by themselves so multiple write clones are probably not super
desirable, but read-only clones should be pretty easy to set up and
keep up-to-date via "bk pull" (or even "bk push" triggered by a commit
script).
You could allow writing on a single read-only clone while the primary
is down and then update the primary when you move back, if that was an
issue, although I'm guessing that the DNS updates would take longer to
propagate than most outages.
I wonder if any of the kernel.org mirror sites would be interested in
hosting a clone of one or more BK repositories.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2003-01-31 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 21:14 Larry McVoy
2003-01-31 21:50 ` Andreas Dilger [this message]
2003-01-31 22:46 ` [Bitkeeper-announce] " Chris Wedgwood
2003-01-31 23:06 ` Anders Gustafsson
2003-01-31 23:07 ` Chris Wedgwood
2003-01-31 23:12 ` Anders Gustafsson
2003-01-31 23:52 ` Andreas Dilger
2003-01-31 22:50 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2002-05-24 17:11 Larry McVoy
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=20030131145018.N3904@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=bitkeeper-announce@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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
all inboxes | Powered by JetHome®