|
Ah yeah, that makes sense. ScopedTaskExecutor does not currently have that support, although I expect it to be added in PM-1809.
|
|
Thanks spencer, this looks like it would only help with the shutdown case (so it doesn't require the outer Executor to be shut down). However, it will not help with the limited number of outstanding tasks that we want to allow. Are there plans to make these ScopedTaskExecutors also support a max number of outstanding tasks?
|
|
This has already been closed so maybe it's moot now, but FYI tommaso.tocci kaloian.manassiev in case you didn't know about it, we now have ScopedTaskExecutor which lets you define a sub-executor that can be shutdown and joined to clean up the tasks scheduled against it, but without actually shutting down the underlying executor/thread pool backing it. Not sure if it would have worked for this use case, but figured I'd mention it since it's a relatively new component and I'm not sure how many people are aware of it.
|
|
Author:
{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}
Message: SERVER-49975 Use separate thread pools for CatalogCache and its loaders
Branch: master
https://github.com/mongodb/mongo/commit/7408f50908d307567e1c4f4b3844e55ad6bd8e01
|
Generated at Thu Feb 08 05:21:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.