Re: recommendations for the 'one writer, many reader' problem?

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: recommendations for the 'one writer, many reader' problem?
From: Joseph Mack <mack.joseph@xxxxxxx>
Date: Thu, 29 Nov 2001 12:06:20 -0500
Matthijs van der Klip wrote:
> Hi,
> Right now I'm using rsync to keep 4 lvs'ed webservers in sync with a
> seperate upload server, but I'm afraid rsync won't last me long. Does
> anyone have any recommendations to solve the 'one writer, many reader'
> problem given the following facts?:
> 1) A docroot of 5GB data, 275K files and growing...

I assume you don't have to update the whole 5G each time, but 
it sounds like you're up against some barrier if not now soon.

This is much the same problem of doing a hot backup of a database
and is one of the reasons that commercial databases cost $$.

You know all the things that I know about. Your only choice
AFAIK is to lay out money or to be crafty and divide your
updates into small self consistent sets. Presumably you could
upload all the new stuff on all machines into a directory with
a unique name (eg has a time and date in it), and when you're ready
to go, to change a link from the old directory to the new directory.


Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center, 
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA

<Prev in Thread] Current Thread [Next in Thread>