sync_client stalls the rest of cyrus while 'no route to host'

[David Carter]

On Sun, 27 Aug 2006, Bron Gondwana wrote:

> To tell you the truth, I'm seriously considering writing a replacement to
> sync_client that does a bunch of different things including multiple
> replicas, maintaining log files, etc.  All of this drops out pretty easily
> from a pattern which produces a single log file per day and calls the
> sync_client fork children with a byte-range on the log file to run rather
> than moving the file and then running the copy.

I think that you would be better off with multiple log files and multiple
sync_client processes, one for each replica. That way each replication
stream is independent and can progress at its own best speed.

Particularly important if a replica dies (or is shut down for routine 
maintenance) and needs to catch up from a big backlog of transactions.

-- 
David Carter                             Email: David.Carter at ucs.cam.ac.uk
University Computing Service,            Phone: (01223) 334502
New Museums Site, Pembroke Street,       Fax:   (01223) 334679
Cambridge UK. CB2 3QH.