[SERVER-51445] Must destroy retryableOperation before entering Complete in initial_syncer Created: 08/Oct/20 Updated: 29/Oct/23 Resolved: 22/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2020-10-19, Repl 2020-11-02 |
| Participants: |
| Description |
|
In certain cancellation scenarios, the InitialSyncer will be canceled with a retryableOperation still active. If this operation is active when the InitialSyncer is destroyed, it will access an already-destroyed InitialSyncSharedData. So we must destroy it in _finalCallback
This was found in BACKPORT-7799 and so does not need to be backported to 4.4.
|
| Comments |
| Comment by Githook User [ 21/Oct/20 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |