[SERVER-56437] ReshardingDonorOplogIterator destroys OperationContext with Pipeline still attached on exception Created: 28/Apr/21  Updated: 29/Oct/23  Resolved: 29/Apr/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-oplog-apply
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-57653 ReshardingDonorOplogIterator must cal... Closed
related to SERVER-57654 Call Pipeline::dispose() if Pipeline:... Closed
related to SERVER-57655 Call Pipeline::dispose() if Pipeline:... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-05-03
Participants:
Linked BF Score: 170
Story Points: 1

 Description   

This leads to an invariant failure when destroying the OperationContext due to storage resources still be in use by the Pipeline. ReshardingDonorOplogIterator::_pipeline must either be detached from the OperationContext on exception or destroyed before the OperationContext is destructed on exception.



 Comments   
Comment by Githook User [ 29/Apr/21 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-56437 Always detach Pipeline from OperationContext.
Branch: master
https://github.com/mongodb/mongo/commit/b72f3ee9ad13009ae0dbc70179d618577894361a

Generated at Thu Feb 08 05:39:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.