Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.0.3
-
None
-
Untriaged
-
1
-
Unknown
Description
Multiple callbacks are allowed to run for metakv listener. These normally run fine as these do not take much time. But in-case the callbacks take time (e.g due to long DNS look-up time) then the order in which changes happen in metakv are applied out-of-order.
This is because the a spawned callback gets stalled and in the meantime, the metakv gets modified. This stalled callback overrides with values.
All this gets manifested with error:
Error writing to metakv: revision number does not match
|
Attachments
Issue Links
- backports to
-
MB-54366 [BP-7.0.5] - XDCR Metakv callbacks racing when remote cluster ref is added/changed
- Resolved
-
MB-54431 [BP-7.1.3] - XDCR Metakv callbacks racing when remote cluster ref is added/changed
- Resolved
- causes
-
MB-54424 XDCR - Unexpected server error (500)
- Closed
- relates to
-
MB-57719 XDCR - metakv "revision does not match" shows up
- Closed
-
MB-57787 [BP 7.2.1] - XDCR - metakv "revision does not match" shows up
- Closed
-
MB-57788 [BP 7.1.5] - XDCR - metakv "revision does not match" shows up
- Closed