-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2019-08-12
-
25
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The test expects that the only lock acquisition that can fail is this global S, by which point we would have updated the value of the 'targetVersion' and 'version' fields. However, if HMAC activates at an inopportune time, we may fail to take locks sooner, as we would have a conflict on the admin database. We should do away with the expectation that the version fields changed, as we already know the downgrade command failed.
- related to
-
SERVER-42439 Parameterize 'failNonIntentLocksIfWaitNeeded' failpoint with optional timeout
-
- Closed
-