I pulled in OpenLDAP 2.4.9 to re-visit some multi-master testing I had done on the previous version. 2.4.9 was a better experience for me than 2.4.8. I re-ran some tests of running two replicated servers on the same machine. I would continuously load in several hundred or thousand user records on one server, then delete them.
The stability is improved from 2.4.8. I have yet to have a server core on me--even after abruptly shutting done one or both servers during a batch load or delete.
My only issue now is that when performing a bulk load, if you interrupt the client during the load ( Control-c ldapadd ) the servers get out of sync. The server you directly attach to in order to load the records contains more records than the "replicated" server. Under most circumstances, this would not be a huge issue, but it does show an easy way for a client to get the servers out of sync.
With the 2.4.9 release of OpenLDAP, I would trust the multi-master synchronization enough now for use on production systems.
5 comments:
Please do take your time to post any funnies to the openldap mailing lists.
Cheers.
Hello, I have a problem with openLDAP 2.4.9 and multimaster, this is the case:
I have 2 masters (A,B) running.
Master B dies, now I am working with just one master and an administrator performs adds, updates and deletes meanwhile.
Master A dies too, I restart master A and master B, but if I compare theirs DITs master B has performed some changes but not all.
The deletes are not performed (adds & updates are ok)
Grettings
Miguel Angel
Sorry by the bad english
There have been fixes for this, 2.4.11 will be out very soon (this week)
Post a Comment