Since we can not compare
this "replicated ruv" to the replicas tombstone ruv, we can
instead compare the "replicated ruv" to the ruv in the
replica's repl agreement(unless it is a dedicated consumer -
here we might be able to still look at the db tombstone ruv
to determine the status).
Problems with this approach:
- All the servers need to have the same replication
configuration(the same fractional replication policy and
attribute stripping) to give accurate results.
- If one replica has an agreement that does NOT filter the
updates, but has agreements that do filter updates, then we
can not correctly determine its synchronization state with
the fractional replicas.
- Performance hit from updating another ruv(in cn=config)?
Fractional replication simply breaks our monitoring
process. I'm not sure, not without updating the repl
protocol, that we can cover all deployment scenarios(mixed
fractional repl agmts, etc). However, I "think" this
approach would work for most deployments(compared to none at
the moment). For IPA, since they don't use consumers, this
approach would work for them. And finally, all of this
would have to be handled by a updated version of
repl-monitor.pl.
This is just my preliminary idea on how to handle this.
Feedback is welcome!!
Thanks in advance,
Mark
