|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:
|For Gerrit Dashboard: MB-57234
|MB-57234: backfillMgr to not hang on spec callback for non-KV nodes