Description
Last time we tried to add scopes and move it out of the remote queue group, it was not performant enough, most likely because the normal remote queue faces more contention than having dedicated queues for each version. It may still be performant if it's kept in the remote queue group and uses scopes.
We should potentially remove the strategy of re-creating jobs and instead just schedule a single job, with some kind of backstop logic for cases where the app restarts.
Attachments
Issue Links
- is depended on by
-
SERVER-64731 Switch task generation to be done at the version level for mongodb-mongo-master
-
- Closed
-
-
EVG-16019 Error to translate project should cause generate-tasks to fail immediately
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
EVG-13834 Some generate.tasks jobs run significantly later than when they are enqueued
-
- Closed
-