Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Ayush NayyarAyush NayyarReporter
Neil HuangNeil HuangIs this a Regression?
YesTriage
UntriagedStory Points
0Priority
MajorInstabug
Open Instabug
Details
Details
Assignee
Ayush Nayyar
Ayush NayyarReporter
Neil Huang
Neil HuangIs this a Regression?
Yes
Triage
Untriaged
Story Points
0
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created June 2, 2023 at 5:40 PM
Updated February 6, 2025 at 6:43 PM
Resolved June 15, 2023 at 9:17 PM
Issue
Resolution
When a replication spec change was made to a non-Data Service node, delete replication hung and caused the node to return an incorrect replication configuration.
XDCR now checks that the node is running the Data Service and handles it correctly.
Create a 2-node source cluster, 1-node target cluster. 1 source node is KV and 1 source node is back up (anything but KV)
Create replication, delete replication, repeat 6x, which will fill up the channel.
Capture go-routine of the non-KV source node, and we can see the lock contention: