provider and consumer in 2.4.24 -> same behaviourGet rid of session log -> same behaviour

If I removed one of the providers of my consumer, everything went fine. Even, if I stop the consumer during mass deletes, it sync very fast as soon as it starts again
That's related to several providers for one consumer and may be something else I don't see.The second provider (first rid in my conf) has less that 15 entries and no updates at all.

I changed the order of the providers in my slapd.conf. There is no difference.

Should we use a session log? I'll try without. That's tricky to understand each parameter.Would be great to have something anaylizing more than syntax, relations between parameters and database cache optimization.

I was obliged to remove slapd package on consumer. Then compile in 2.4.24 and
restart. doing the same tests, there was nothing diffferent. provider is still
2.4.23
My test: delete 30000 entries, stop consumer when deleting; start again
consumer when it's finished. Consumer is then out of sync.

You haven't posted your provider config. It appears you're using syncprov-sessionlog. Obviously both ends of this system are vital to solving the puzzle.

We were told to migrate to 2.4.23 sometimes ago, and we did some work to
update our production servers. Can I try 2.4.24 only on the consumer side?
It would be a pain to migrate all servers to 2.4.24 without package.

I am testing the replication feature in a multimaster environment
replicating
into a single database. As stated before, I added serverid to my
providers. I
just have two providers for test purpose.
I tested mass updates on a provider, stopped my replica during
updates, then
start again and it's OK, it updates the entries
If I do the same for mass deletes. I deleted 40000 entries while
stopping the
consumer. My consumer is still with 30000 undeleted entries. I
left the
consumer for hours, restarting it twice.
It seems there is no regular compare between consumer or provider
in such
situation. I'll simplify to test in a single provider setup, to
see if it works.