[SERVER-81109] Fix internal_transactions_sharded_from_mongod.js's handling of causal consistency across sessions Created: 15/Sep/23 Updated: 26/Sep/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Cheahuychou Mao |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-nyc-subteam3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding NYC
|
||||
| Participants: | |||||
| Linked BF Score: | 5 | ||||
| Description |
|
internal_transactions_sharded_from_mongod.js uses different sessions within the same FSM thread, and its logic requires read-your-own-writes guarantees even across different sessions. Therefore, verifyDocuments should use a causal consistent session and call 'advanceClusterTime(max cluster time of this.sessions)' and advanceOperationTime(max operation time of this.sessions). The bumpClusterTime should then be removed altogether. |