-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Sharding EMEA
-
Fully Compatible
-
ALL
-
Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10
-
164
-
None
-
None
-
None
-
None
-
None
-
None
-
None
To enable replay protection, the collmod participant command must be called with a sessionId and a txnNumber.
This means that any local command executed by the collmod participant will reuse the sessionId and txnNumber attached to the opCtx, leading to a deadlock since the sessionId is already checked out by the collmod participant command itself.
To solve this we need to create a newly fresh opCtx through an AlternativeClientRegion.
In addition, we'll solve the following issue under this task too:
The OSI fields are not being appended to the command request since this line does not modify the BSON object in place, it just returns a new merged BSONObj that is not used at all.
- is caused by
-
SERVER-73538 Add replay protection to the acquisition/release of the critical section in the collmod coordinator
-
- Closed
-
- is duplicated by
-
SERVER-77447 Fix timeout in timeseries_coll_mod.js due to OperationSessionInfo being appended in collmod_coordinator.cpp
-
- Closed
-