XDCR should be incremental on topology changes
Description
Components
Fix versions
Environment
None
Release Notes Description
None
blocks
depends on
Activity
Show:
Arunkumar Senthilnathan December 7, 2021 at 6:15 PM
Automation is done - jobs running on jenkins and results available on greenboard
Neil Huang October 8, 2021 at 7:46 PM
Marking resolved as the two milestones (https://couchbasecloud.atlassian.net/browse/MB-47923#icft=MB-47923 + https://couchbasecloud.atlassian.net/browse/MB-48124#icft=MB-48124) have been submitted
Chaitra Ramarao June 25, 2020 at 7:19 AM
@Neil Huang - is this still targeted for CC?
Chris Malarky August 13, 2018 at 5:40 PM
Thanks @Yu Sui!
Yu Sui August 13, 2018 at 5:11 PM
Yes, it is in mad-hatter plan.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Reporter
Anil Kumar
Anil Kumar(Deactivated)Priority
Critical
Instabug
Open Instabug
PagerDuty
PagerDuty Incident
PagerDuty Incident
Sentry
Linked Issues
Linked Issues
Zendesk Support
Linked Tickets
Linked Tickets
Created January 22, 2014 at 6:39 AM
Updated August 29, 2023 at 4:19 PM
Resolved October 8, 2021 at 7:46 PM
Instabug
Currently, XDCR checkpoints are not replicated to the replica nodes. this means that on any topology change, XDCR needs to re-check if each item is needed on the other side. While it may not resend the data, rechecking for a large number of items is quite expensive.
We need to replicate checkpoints so that XDCR is incremental on topology changes just as it work without topology changes.