[Production] Switch to elasticache celery broker#6824
Merged
Conversation
Dedicating two celery machines to reading from the old broker to ensure load is handled properly.
gherceg
force-pushed
the
gh/prod/elasticache-celery-broker
branch
from
a7d5b42 to
e729474
Compare
millerdev
approved these changes
Mar 6, 2026
millerdev
approved these changes
Mar 10, 2026
Contributor
Author
|
Fully cut over! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://dimagi.atlassian.net/browse/SAAS-19089
This PR includes the terraform changes necessary to create a new elasticache cluster running redis, and a new r53 record to enable easy routing to the cluster.
It then handles updating the variables used by commcare services to interact with the message broker, and then sets
celery_broker_migrationto true on the celery_b2 group so that machines in that group continue to read messages from the OLD_BROKER_URL to ensure all messages are drained.To roll this out, I'll first run terraform apply on production to create the cluster. Once I confirm the cluster has been created successfully, I will follow the steps outlined in https://dimagi.atlassian.net/wiki/spaces/cc/pages/3522330836/Migrating+Celery+Brokers to perform the migration.
Environments Affected
Production