The lsid and txnNumber fields will become legitimate top-level values for all commands. As such, there should be code just after command parsing, but before authentication (so the sessionId is available to the auth system), which extracts these fields and sets them on the OperationContext.
- is documented by
-
DOCS-10444 Docs for SERVER-29852: Store logical session id and transaction number on the OperationContext
- Closed
- related to
-
SERVER-30936 Attempting to create an existing sharded collection causes mongos to crash when using a logical session id
- Closed