Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.0.0-rc0, 6.0.7, 5.0.19
Affects Version/s: None
Component/s: Sharding
Labels:
- shardingemea-qw

Assigned Teams:

Sharding EMEA
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v6.3, v6.0, v5.0, v4.4
Sprint:
Sharding EMEA 2022-07-25, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-04-17
Linked BF Score:
35
Story Points:
1
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

This could lead us to some memory leaks.

Note that the mongos shutdown procedure shutdowns the ExecutorPool.

is related to

SERVER-67077 TransactionCoordinator uses both the Grid fixed executor and the executor on the AsyncWorkScheduler

Open

SERVER-51316 Grid executor pool should be shut down on mongod shutdown

Closed

SERVER-73588 Suppress memory leak notification about canceling migrations on shutdown

Closed

related to

SERVER-78971 Skip shutting down Grid::getExecutorPool() when TestProctor is disabled

Closed

Assignee:: Antonio Fuschetto
Reporter:: Sergi Mateo Bellido
Participants:: Antonio Fuschetto, Githook User, Liubov Molchanova, Sergi Mateo Bellido
Votes:: 0 Vote for this issue
Watchers:: 10 Start watching this issue

Created:: Jul 01 2022 11:10:52 AM UTC
Updated:: Apr 17 2024 04:45:42 PM UTC
Resolved:: Apr 06 2023 07:10:51 AM UTC
Confidence Status Last Update:: 04/Apr/23 7:57 AM