[SERVER-33245] mr.cpp can throw in an ON_BLOCK_EXIT handler when there's already an active exception Created: 09/Feb/18  Updated: 29/Oct/23  Resolved: 22/Feb/18

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.6.7, 3.7.3

Type: Bug Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-35749 MapReduce throws exception within ON_... Closed
is duplicated by SERVER-35772 Stepdown under ScopeGuard causes MapR... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: Repl 2018-02-26
Participants:
Linked BF Score: 61

 Description   

We've seen this happen in this particular ON_BLOCK_EXIT, but there may be other spots in this file as well. In one observed failure, there is an initial exception being thrown during the command execution within a try/catch, and the subsequent ON_BLOCK_EXIT method throws again which results in two active exceptions. Certainly the server shouldn't crash but there's no obvious way to remove the temp collection now that the node is no longer the primary.



 Comments   
Comment by Githook User [ 03/Aug/18 ]

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-33245 add unit test for primary step down during mapReduce

(cherry picked from commit c0480b762f7b155ca0a06921acf99fc31859ea85)
Branch: v3.6
https://github.com/mongodb/mongo/commit/c8832428acc6804d0c23645e6026cd4d413da6be

Comment by Githook User [ 03/Aug/18 ]

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-33245 remove unnecessary ScopeGuard for dropTempCollections() from mapReduce

(cherry picked from commit d4c4f81b7695c394dcb353be55d33a2c523518af)
Branch: v3.6
https://github.com/mongodb/mongo/commit/2b5a3a10c1ddf159d35fe05a739f2b20416c249c

Comment by Githook User [ 03/Aug/18 ]

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-33245 propagate Database::dropCollection() errors when dropping temporary colleciton and incLong in mapReduce

(cherry picked from commit 4af395056581dd6222ae301419ff5ad8b1ba1e17)
Branch: v3.6
https://github.com/mongodb/mongo/commit/71d343f33c56cd11bab52062251a86a9b974d9b2

Comment by Githook User [ 03/Aug/18 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-33245 improve PrimarySteppedDown and State destructor error messages in mapReduce

(cherry picked from commit 0628b8ee3ce53f7263393ed2112ef79d6b32bcba)
Branch: v3.6
https://github.com/mongodb/mongo/commit/27216e9d263cea22829edf8ff6d859c914641836

Comment by Githook User [ 22/Feb/18 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-33245 add unit test for primary step down during mapReduce
Branch: master
https://github.com/mongodb/mongo/commit/c0480b762f7b155ca0a06921acf99fc31859ea85

Comment by Githook User [ 17/Feb/18 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-33245 remove unnecessary ScopeGuard for dropTempCollections() from mapReduce
Branch: master
https://github.com/mongodb/mongo/commit/d4c4f81b7695c394dcb353be55d33a2c523518af

Comment by Githook User [ 17/Feb/18 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-33245 propagate Database::dropCollection() errors when dropping temporary colleciton and incLong in mapReduce
Branch: master
https://github.com/mongodb/mongo/commit/4af395056581dd6222ae301419ff5ad8b1ba1e17

Comment by Githook User [ 16/Feb/18 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-33245 improve PrimarySteppedDown and State destructor error messages in mapReduce
Branch: master
https://github.com/mongodb/mongo/commit/0628b8ee3ce53f7263393ed2112ef79d6b32bcba

Comment by Charlie Swanson [ 16/Feb/18 ]

Looks like this happened at least one other time, throwing back in 'Needs Triage' for re-evaluation.

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