It seems the problem is with a single replica only. Is was assigned request id range
19990001-20000000. Requests 19990001-19990008 were submitted some time ago, and requests
19990001-19990005 were overwritten in my recent attempts to install another replica. Note
that CA doesn't always overwrite the first request, it actually increments request
number, but still reusing already assigned ids.
Trying to install a replica one or two more times will solve the problem as CA will
naturally start using previously unused request ids (I'm planning to restore
overwritten requests from backup after that). But I don't like this solution because
it doesn't tell us what exactly happened, why did it happen and how to avoid it in the
future.
That being said, is there a way to verify the problem is actually with VLV indices without
submitting new requests? Running ldapsearch -LLL -x -b
"ou=ca,ou=requests,o=ipaca" -D "cn=Directory Manager" -W
"(requeststate=*)" on every replica shows all the requests 19990001-19990008.
Maybe you could point me to the exact mechanism / query / source code snippet used to
select the next request id?
Regards,
Boris