[GitHub] [superset] LuPan2015 opened a new issue #18697: How does superset worker ensure that every task is executed only once？

[GitBox <gi...@apache.org>]

LuPan2015 opened a new issue #18697:
URL: https://github.com/apache/superset/issues/18697


   In superset beat, the ID of the scheduled task that meets the conditions will be written to redis. If there are multiple workers at the same time, how to ensure that each task is executed only once?


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

[GitHub] [superset] zhaoyongjie commented on issue #18697: How does superset worker ensure that every task is executed only once？

[GitBox <gi...@apache.org>]

zhaoyongjie commented on issue #18697:
URL: https://github.com/apache/superset/issues/18697#issuecomment-1038607778


   Hi @LuPan2015, GitHub issue list is used to track bugs now, so I transfer this topic to the discussion board.


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org