Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
ALL
-
Sharding 2020-08-24
-
0
Description
The ReplicaSetAwareService test is mistakenly ending up calling the VectorClockMongoD onStepUpComplete.
So far the test has always worked because such method call always resulted in a NOP, but that will not be the case anymore with the changes that are going to be introduced in SERVER-49193.
Attachments
Issue Links
- is depended on by
-
SERVER-49193 Recover the VectorClock on shard primary step up
-
- Closed
-
- related to
-
SERVER-46201 Implement a generic ReplicaSetStateAwareService
-
- Closed
-