Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If there are some replicas cannot catch up with the leader due to that are slow network, disk issue, ... etc while log truncation for LMLE, it will cause the mirroring pending or in FAILED state. In this case, users should manually resolve the issue, or re-assign the replicas into other healthy brokers, and start the mirroring again.


Dynamic "mirror.support.unclean.leader.election" config

Because the new added mirror.support.unclean.leader.election config is a dynamic configuration, it could be enabled in the middle of the mirroring, not at the beginning of the mirroring.