From e9ab422101f6e20b07d762b29c75029ffbc2c0b7 Mon Sep 17 00:00:00 2001 From: Tim McCormack Date: Mon, 18 Nov 2024 11:54:33 -0500 Subject: [PATCH] feat: Default Celery task protocol to version 2 (by removing setting) (#35865) We've been keeping this pinned to 1, but since we're well past the first version of Celery that can understand both protocol versions, we can just remove the pin. Celery should then default to protocol 2. No action should be required from operators. --- lms/envs/common.py | 9 --------- 1 file changed, 9 deletions(-) diff --git a/lms/envs/common.py b/lms/envs/common.py index 29e90eddfb..d74c28e756 100644 --- a/lms/envs/common.py +++ b/lms/envs/common.py @@ -2844,15 +2844,6 @@ DEBUG_TOOLBAR_PATCH_SETTINGS = False ################################# CELERY ###################################### -# Until we've tested protocol 2, stay with protocol 1. It should be -# fine to just switch to protocol 2, since we're well past celery -# version 3.1.25 (the first version to support it) but we'll want to -# test this in a stage environment first. -# -# - Docs: https://docs.celeryq.dev/en/stable/history/whatsnew-4.0.html#new-task-message-protocol -# - Ticket: https://github.com/edx/edx-arch-experiments/issues/800 -CELERY_TASK_PROTOCOL = 1 - CELERY_IMPORTS = [ # Since xblock-poll is not a Django app, and XBlocks don't get auto-imported # by celery workers, its tasks will not get auto-discovered: