Ticket 48266: Fractional replication evaluates several times the same CSN
In fractional replication if there are only skipped updates and many of them, the supplier
acquire the replica for a long time. At the end of the session, RUV is not updated
so the next session will restart evaluating the same skipped updates
The fix introduces subentries under the suffix: 'cn=repl keep alive <rid>,$SUFFIX'
During an incremental replication session, if the session only contains skipped updates
and the number of them overpass a threshold (100), it triggers an update on that subentry.
This update will eventually be replicated, moving forward the RUV
Reviewed by: Noriko Hosoi, Rich Megginson, Simon Pichugin
Platforms tested: <plat>
Flag Day: no
Doc impact: no