[SERVER-38371] Session catalog migration will skip later sessions if a different earlier session encounters new transaction Created: 03/Dec/18 Updated: 29/Oct/23 Resolved: 05/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.9, 4.0.4 |
| Fix Version/s: | 3.6.10, 4.0.5, 4.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.0, v3.6
|
||||
| Sprint: | Sharding 2018-12-17 | ||||
| Participants: | |||||
| Description |
|
Migration of the sessions catalog needs to be prepared to find a new transaction already started on the recipient shard for an older session it is migrating from the donor. Because of the place where this try/catch block is placed though, such a condition will skip all the sessions that follow, meaning that there will be incomplete session information on the recipient shard. |
| Comments |
| Comment by Githook User [ 07/Dec/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit f036c87b5f4c9d6a82338aa8680b5c6f2b541026) |
| Comment by Githook User [ 05/Dec/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit 04ba7e4186bff4d58558b63855291718d97ee35f) |
| Comment by Githook User [ 05/Dec/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |