--On Thursday, November 23, 2023 5:33 PM +0000 falgon.c...@gmail.com wrote:
b) olcLogLevel: stats sync - We running our tests with stats only. Meheni probably left this configuration to check before sending the config here.
My point was more that it should be a multi-valued attribute with unique values not a single valued attribute with 2 strings in the value.
e) Why do you have separate credentions for the monitor db? - sorry for this i don't understand the word credentions. Do you mean credentials ?
Yes, typo
h) For your benchmark test, this is probably not frequent enough, as the purge will never run since you're saying only data - We've run endurance tests to include purging. This settings is from a month ago and we have change this settings multiples times for testing differents setup.To add the purge during tests, we actually set it to 00+01:00 00+00:03. In the final configuration we will probably set it too : 03+00:00 00+00:03. We found that purging every 3 minutes reduced the impact on performance.
While correct that frequent purging is better, you missed my overall point, which is that when you're testing you likely want to purge data on a shorter timescale when doing a benchmark.
I repost a previous question here too : What are the exact messages or errors messages we should find in case of a collision problem?
*If* there are collisions, you'll see the server falling back to REFRESH mode. But only if you have "sync" logging enabled.
syncrepl.c: Debug( LDAP_DEBUG_SYNC, "do_syncrep2: %s delta-sync lost sync on (%s), switching to REFRESH\n", syncrepl.c: Debug( LDAP_DEBUG_SYNC, "do_syncrep2: %s delta-sync lost sync, switching to REFRESH\n",
--Quanah
