Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.5.0
-
Untriaged
-
No
Description
It is possible that remote cluster (half mode encryption) have nodes that run some with scram-sha support, and some without.
This bug is to track and enhance XDCR such that if the target is indeed under this situation, and that remote cluster reference is setup such that it is half-mode encryption, then XDCR should be smart and aware of the target's nodes' setups and not restart pipelines unless target node's mode really changed.
For example, if the target cluster has the following:
node0 - scram-sha
node1 - non scram-sha
node2 - scram-sha
node3 - non scram-sha
Then as the replication pipeline does not need to restart as remote cluster service cycles through the nodes periodically. It should be aware that this set up was the last seen, and no restart is necessary.
When it does change, though, to the following:
node0 - scram-sha
node1 - scram-sha
node2 - scram-sha
node3 - non scram-sha
Then it may be worth restarting the pipeline. This could be thought through some more and discussed.
Attachments
Issue Links
- Clones
-
MB-35542 Compatibility with mixed-mode security settings on Target
- Closed