A generation ID is an id generated when the backend is created or when
data from an ldif (without generation id) is imported. So when setting
up an environment all servers have a different generation ID, to make
replication work you need to choose one server and initialize all
otheres from this server - either by an online total init or by
exporting data to an ldif *with* replication meta data and import this
to the other servers.
Ludwig
On 05/04/2014 04:32 PM, Graham Leggett wrote:
On 04 May 2014, at 3:16 PM, Graham Leggett <minfrin@xxxxxxxx> wrote:
- "Replica has a different generation ID than the local data." - what does this mean? Is it simply information to be ignored, a warning to be heeded (if so, how?), or an error (if so, what action must be taken?).
Picking apart the source code, I find the following code implementing the above message, the code would suggest the message is an error, and that the error is "fatal":
case EXAMINE_RUV_GENERATION_MISMATCH:
slapi_log_error(SLAPI_LOG_FATAL, repl_plugin_name,
"%s: Replica has a different generation ID than the local data.\n",
agmt_get_long_name(prp->agmt));
next_state = STATE_BACKOFF_START;
break;
Does anyone know what a "generation ID" is in the context of two replicas, what it means, what it does? Is the admin in any way involved in the choosing of this "generation ID"?
Why would this "generation ID" be significant when nsds5BeginReplicaRefresh has been set to "start" and the expectation is that server C will be blown away anyway?
Regards,
Graham
--
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
