Re: Some interesting thoughts

[David Boreham <david_list@boreham.org>]

Quanah Gibson-Mount wrote:

> 2) Replica initialization/re-initialization from the master - If you 
> create an attribute "ndsReplicaRefresh" with a hostname as the value 
> in the job class, it will reload that replica's DB, by sending binary 
> indexes over the wire, and then removes the attributes from the job 
> scheduler.  I can only see this working if the master & replica agree 
> on their indexing, however. It also doesn't replicate the replica 
> specific configuration options.


This is not how it works. It sends the entries over the wire, but feeds 
them into the
fast concurrent import code on the replica.

There _is_ an option to initialize a replica using binary indices, but 
you have to
move the data yourself (with ftp or whatever).