[SERVER-66029] Fix lifetime of timers in refineCollectionShardKey transaction callback Created: 27/Apr/22 Updated: 29/Oct/23 Resolved: 02/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc4, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| 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: |
v6.0
|
||||||||
| Sprint: | Sharding 2022-05-02 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 135 | ||||||||
| Description |
|
refineCollectionShardKey uses the transaction API and captures a struct of timers by reference for the API's callback, but the callback runs on an executor so may run after the calling context has gone out of scope after an interruption, like at stepdown. |
| Comments |
| Comment by Githook User [ 02/May/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 5cf29656a8c3a61fb1696efdf8ddad69ca5855dd) |
| Comment by Githook User [ 28/Apr/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |