XDCR can turn OSO mode off at a per-replication level. But, in certain cases where OSO could cause performance issues, we want a fail-safe switch to be able to turn off OSO mode globally.
This fail safe needs to be developed so that it can be applied globally to any currently deployed replications.
|Data streamed from the Data Service over XDCR should always be streamed in order by mutation id. However, in some scenarios, for efficiency, the Data Service streamed records that were not ordered by mutation id. In certain situations, this out-of-sequence-order [OSO] caused performance issues.
|OSO mode is now available as a global override to be switched off for any currently deployed replications to avoid performance issues.