[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Syncrepl with subordinate databases

I see in the man page now under the serverID "Note that this requirement also applies to separate masters contributing to a glued set of databases." I never even looked there. Can the man page be updated to also mention the serverID requirement under the subordinate section. 



On Thu 24 Oct 2013 06:34:11 PM PDT, Howard Chu wrote:

Robert Minsk wrote:

A summary of what I posted below .  I have several subordinate
databases and
each subordinate database acquires there data via a refreshOnly
syncrepl.
Instead of storing the contextCSN on the subordinate database the
contextCSN
gets stored on the superior database.  As a result the superior
databases
contextCSN is the maximum of the subordinate databases.  This causes
all but
the syncprov server with the latest contextCSN to abort the sync with
"consumer state is newer than provider!"

It seems a configuration option needs to be added that allows storing
and
reading of the contextCSN on the subordinate databases as well as the
maximum
contextCSN on the superior database.


Use a unique ServerID per provider.



--
Robert Minsk
Systems and Software Engineer

WWW.METHODSTUDIOS.COM <http://www.methodstudios.com>
730 Arizona Ave, Santa Monica, CA 90401
O:+1 310 434 6500 <tel:+13104346500> // F:+1 310 434 6501
<tel:+13104346501>

Los Angeles <http://www.methodstudios.com/signature/url/los-angeles>

This e-mail and any attachments are intended only for use by the addressee(s) named herein and may contain confidential information. If you are not the intended recipient of this e-mail, you are hereby notified any dissemination, distribution or copying of this email and any attachments is strictly prohibited. If you receive this email in error, please immediately notify the sender by return email and permanently delete the original, any copy and any printout thereof. The integrity and security of e-mail cannot be guaranteed.