[SERVER-30880] Handle migration of sessions with incomplete history Created: 29/Aug/17  Updated: 30/Oct/23  Resolved: 25/Oct/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.12
Fix Version/s: 3.6.0-rc2

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-10-02, Sharding 2017-10-23, Sharding 2017-11-13
Participants:

 Description   

because the oplog rolled over. This shouldn't cause the migration to fail, as this might just be a session that is too old that the user won't ever reference it again. However, the recipient shard should also have a way of knowing that it has accepted an incomplete history so when it can error our appropriately when the user attempts to perform a retryable write on the same transaction.



 Comments   
Comment by Githook User [ 25/Oct/17 ]

Author:

{'email': 'randolph@10gen.com', 'name': 'Randolph Tan', 'username': 'renctan'}

Message: SERVER-30880 Handle migration of sessions with incomplete history
Branch: master
https://github.com/mongodb/mongo/commit/67f735e6705091659e2a8cf46a9285f09bcf749a

Generated at Thu Feb 08 04:25:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.