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.
This commit is contained in:
Tim McCormack
2024-11-18 11:54:33 -05:00
committed by GitHub
parent a34a54d29f
commit e9ab422101

View File

@@ -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: