The vector clock document update is currently performed waiting for majority write concern up to 60 seconds before returning a WriteConcernFailed exception to the caller.
As persisting the new configTime|topologyTime is required for ensuring causal consistency, callers must wait indefinitely for the updated times to be persisted. The write concern must not have a timeout and only fail in case of step-downs.
- is related to
-
SERVER-62213 Investigate presence of multiple migration coordinator documents
-
- Closed
-
-
SERVER-49192 Persist the VectorClock for configTime and topologyTime casual consistency
-
- Closed
-
- related to
-
-
- Closed
-