nicolavolpini commented on issue #22664: URL: https://github.com/apache/superset/issues/22664#issuecomment-3112623993
> They are different task Ids. Have you started multiple Celery Beat Instance? This was indeed our problem. We run Superset as an AWS ECS deployment and had 2 Celery Beat instances running. Once dropped down to 1, duplicate reports stopped. It is also recommended in the Superset docs: > There should only be one instance of celery beat running in your entire setup. If not, background jobs can get scheduled multiple times resulting in weird behaviors like duplicate delivery of reports, higher than expected load / traffic etc. Source: https://superset.apache.org/docs/configuration/async-queries-celery/ Might not be the root cause for everyone but I thought it would be beneficial to report the solution nevertheless, for anyone who is reaching this ticket via web search. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
