Re: [Handle-info] Handle server mirror replication howto - questions

[Robert Tupelo-Schneck <schneck@cnri.reston.va.us>]

On 2012-12-13, at 10:02 , Eric Auer wrote:
>> However, as currently implemented, handle server replication assumes that the servers in a replication group will be identical.  There is no provision for a server replicating from several sources of distinct handles.  Is there demand for such a feature?
> 
> I did not understand that one...

I mean, if server A serves prefix 123 (and not 456), and server B serves prefix 456 (and not 123), you couldn't create a mirror that replicates both A and B and serves both 123 and 456.


>> The mirror will also need a txnsrvsv.bin file.  This file is the siteinfo.bin of the primary server, and is used by the mirror to locate and authenticate the primary.
> 
> Interestingly, the mirror where I looked did not have this file and
> it seems to be stuck in a loop of 'full redump needed' warnings...?

I should have said "txnsrcsv.bin".  There is another way to configure replication using a "replication_sites_handle" value in the server_config.  That handle is resolved to find the site information for servers to replicate from.

The full redump needed indicates that the primary thinks your server is too far out of date.  Stop the mirror and run the "hdl-dumpfromprimary" script, it will pull all the information from the primary.  Then you can restart and replication should continue normally.



>> In fact, which prefixes are homed will be determined by the primary server and replicated to the mirror.  No action is required.
> 
> So you do not have to home anything to the mirror, nor have to tell
> the mirror which prefixes to mirror, as all that is in txnsrvsv.bin?

It's not in the txnsrcsv.bin, but the primary server will send all that information to the secondary.

Best,
Robert


_______________________________________________
Handle-Info mailing list
Handle-Info@cnri.reston.va.us
http://www.handle.net/mailman/listinfo/handle-info