Replies: 2 comments 1 reply
-
|
This is a frequently reported issue after upgrading to v1.14.0+. The task storm is not a bug — it's caused by a backlog of accumulated What happened: Prior to v1.14.0, the Fix — purge the backlog: # Stop the worker first
docker compose stop worker
# Purge accumulated tasks from Redis (adjust -n if your Redis DB number differs)
redis-cli -n 1 UNLINK trigger_refresh_publisher
# Restart
docker compose up -dAfter purging, the task will settle into its normal once-per-minute cadence. This has been confirmed working by multiple users [2] [3]. Alternative: If you don't use trigger/OAuth providers, you can disable the task entirely by adding To reply, just mention @dosu. Share context across your team and agents. Try Dosu. |
Beta Was this translation helpful? Give feedback.
-
|
Could you provide the configuration details of your server, such as the number of CPU cores and the amount of RAM? Also, do you have any custom settings or overrides in your |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
when deploying docker compose version 1.14.2 on a single server.
After upgrading from version 1.10.1-fix.1 to 1.14.2, a large number of continuous refreshers occur. How to solve this problem?
2. Additional context or comments
No response
Beta Was this translation helpful? Give feedback.
All reactions