Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Ayush NayyarAyush NayyarReporter
Neil HuangNeil HuangStory Points
0Priority
MajorInstabug
Open Instabug
Details
Details
Assignee
Ayush Nayyar
Ayush NayyarReporter
Neil Huang
Neil HuangStory Points
0
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created May 8, 2023 at 10:00 PM
Updated September 19, 2023 at 10:23 AM
Resolved June 6, 2023 at 5:39 PM
XDCR can turn OSO mode off at a per-replication level, or at a default 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.
Issue
Resolution
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.