> >> > > It's not the "post init" operations I'm worried about. > > > > It's that operations that were part of the init to the consumer are > > replayed from the changelog. > > > > Operations that occurred after the init starts, definitely still need to > > be replayed, and this makes sense. > > > > Lets say we have: > > > > 1 - insert A > > 2 - insert ou=B > > 3 - modrdn A under ou=B > > 4 - insert C > > xxxxxx <<-- We start to transmit the data here. > if we start the total update here, the supplier will send its RUV in the > start repl request, it will be set as RUV in the consumer after total > init is complete. > it skips to send the ruv entry Are you sure? The behaviour that people are claiming to see would contradict this behaviour. Certainly there have been a number of fixes in URP related to replaying modrdn's and related changed after an online init .... > > > > Does that make sense? > yes, and I think that is what it is doing now I don't think it is .... -- Sincerely, William Brown Software Engineer Red Hat, Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
-- 389-devel mailing list 389-devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
