Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow disable celerbeat programmatically #704

Closed
alexdlaird opened this issue Oct 10, 2024 · 1 comment
Closed

Allow disable celerbeat programmatically #704

alexdlaird opened this issue Oct 10, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@alexdlaird
Copy link
Member

This way we could autoscale fleet without running more than one beat instance (as that creates duplicate tasks).
@alexdlaird
Copy link
Member Author

The proper solution to this is to build worker and beat as separate Docker files. celerbeat should only be provisioned in one of the container's built. beat and worker can then be deployed as separate task definitions, ensuring beat only ever has 1 instance, but worker can be scaled as needed.

@alexdlaird alexdlaird added the enhancement New feature or request label Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexdlaird