Description
GOXDCR does not have an easy way to handle NOT_MY_VBUCKET errors other than restarting. This is because GOXDCR caches vb server map in several components and it is not easy for GOXDCR to handle changes to the vb server map, which is what the NOT_MY_VBUCKET error typically indicates, when replication is still running.
Attachments
Issue Links
- relates to
-
MB-20093 [CLONE] GoXDCR should not restart when it receives a NOT_MY_VBUCKET response
- Closed
For Gerrit Dashboard: MB-18949 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
65420,3 | MB-18949 final - make pipeline restart less frequently when receiving not_my_vb error from target | master | goxdcr | Status: ABANDONED | 0 | 0 |
65526,3 | MB-18949 make pipeline restart less frequently when receiving not_my_vb error from target | sherlock | goxdcr | Status: MERGED | +2 | +1 |
65527,3 | MB-18949 parallelize checkpointing from topology changes | sherlock | goxdcr | Status: MERGED | +2 | +1 |
66355,2 | CBQE-0: Fixing pause resume and failover testcases by increasing timeout owing to MB-18949 | master | testrunner | Status: MERGED | +2 | +1 |