fix: Update runservice worker scripts to disable unneeded features #1371
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.
We've encountered issues where workers would stop receiving tasks after an error message like this:
I was able to reproduce this locally via Docker by manually bouncing the Redis container.
After some research, we came across suggestions to disable the heartbeat/gossip/mingle features of Celery. In my local testing it appears this change eliminates (or at least reduces) the issue where the workers cannot reconnect to Redis after a connection failure.
We have been running this in production for over a month and everything works as expected, including Flower.