Description
xdcr replication periodically checks source bucket status. If the uuid of the source bucket changes, the replication gets itself deleted. When the check for source bucket status fails with an error that is not "bucket does not exist", replication incorrectly executes the same code path as the scenario above and gets itself deleted. This needs to be fixed
Attachments
Issue Links
- relates to
-
MB-24743 xdcr incorrectly deletes replication when fails to check source bucket status
- Closed
For Gerrit Dashboard: MB-24832 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
79436,3 | MB-24832 fix error handling when fail to get bucket info for source and target bucket | watson | goxdcr | Status: MERGED | +2 | +1 |
79440,3 | MB-24832 fix error handling of parse errors | watson | goxdcr | Status: MERGED | +2 | +1 |
79460,2 | MB-24832 fix issue with elastic search target cluster | watson | goxdcr | Status: MERGED | +2 | +1 |