Dear Folks,
I am trying to improve my understanding of the RID before making many large deployments of syncrepl.
My understanding is that the replica ID (RID) is unique within one level of [provider] --> [consumer], [consumer],... relationship.
Here, an arrow --> represents replication of one directory tree from provider to consumers, and commas represent consumers at the same level, all replicating from the same provider, and the square brackets [...] represent one machine.
1. If there is a relationship like this, where at least one machine acts simultaneously as consumer and provider [provider] --> [consumer+provider] --> [consumer], [consumer],...
does the RID need to be unique within all these consumers at all levels in the propagation of replication?
2. What are the consequences of changing the RID on a consumer? Would this inevitably require a dump and restore? Is the RID stored in the data? Where is it stored, besides in the consumer's syncrepl configuration?
Nick Urbanik wrote:
Dear Folks,
I am trying to improve my understanding of the RID before making many large deployments of syncrepl.
My understanding is that the replica ID (RID) is unique within one level of [provider] --> [consumer], [consumer],... relationship.
That is not what the documentation says. Where did you get this understanding?
An RID is just a unique tag within a single slapd.conf or slapd.d. Its only purpose is to provide an unambiguous ID that can be referenced from the slapd -c option. That's all.
Dear Howard,
On 22/06/10 07:31 -0700, Howard Chu wrote:
Nick Urbanik wrote:
Dear Folks,
I am trying to improve my understanding of the RID before making many large deployments of syncrepl.
My understanding is that the replica ID (RID) is unique within one level of [provider] --> [consumer], [consumer],... relationship.
That is not what the documentation says. Where did you get this understanding?
I misunderstood the documentation :-/
An RID is just a unique tag within a single slapd.conf or slapd.d. Its only purpose is to provide an unambiguous ID that can be referenced from the slapd -c option. That's all.
Thank you very much for your helpful clarification.
--On Tuesday, June 22, 2010 12:00 PM +1000 Nick Urbanik nick.urbanik@optusnet.com.au wrote:
Dear Folks,
I am trying to improve my understanding of the RID before making many large deployments of syncrepl.
The RID uniquely identifies a syncrepl stanza inside the replica for a given database. If you have more than one syncrepl statement in a replica's configuration, they must all have a unique rid. Other replicas and consumers know nothing of the RID inside a different replica's setup.
In most of my setups, I have a single syncrepl stanza on the replicas, so I use the same RID on all of them.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Dear Quanah,
On 22/06/10 08:04 -0700, Quanah Gibson-Mount wrote:
--On Tuesday, June 22, 2010 12:00 PM +1000 Nick Urbanik nick.urbanik@optusnet.com.au wrote:
Dear Folks,
I am trying to improve my understanding of the RID before making many large deployments of syncrepl.
The RID uniquely identifies a syncrepl stanza inside the replica for a given database. If you have more than one syncrepl statement in a replica's configuration, they must all have a unique rid. Other replicas and consumers know nothing of the RID inside a different replica's setup.
In most of my setups, I have a single syncrepl stanza on the replicas, so I use the same RID on all of them.
Thank you. Your clarification is very helpful.
openldap-technical@openldap.org
-
Howard Chu -
Nick Urbanik -
Quanah Gibson-Mount