[SERVER-51316] Grid executor pool should be shut down on mongod shutdown Created: 02/Oct/20  Updated: 05/Jul/22  Resolved: 20/Nov/20

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

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Won't Fix Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-67732 mongod shutdown procedure doesn't shu... Closed
Operating System: ALL
Sprint: Sharding 2020-11-02, Service arch 2020-11-30
Participants:
Linked BF Score: 145

 Description   

In mongos, we shut down the Grid's executor pool. We don't do the same for mongod which can lead to leaks.

We should at least shut down the executor - I'm not sure if we want to join it or not though since it might take a little while to join and that would slow down shutdown.



 Comments   
Comment by Matthew Saltz (Inactive) [ 20/Nov/20 ]

We were intentionally not shutting down this executor because we also don't want to join it, in case there are tasks that take a long time to resolve. Closing in favor of SERVER-51317 as the fix to BF-18913

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