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.

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

handle celery worker limit #505

Open
gubuntu opened this issue Nov 22, 2018 · 1 comment
Open

handle celery worker limit #505

gubuntu opened this issue Nov 22, 2018 · 1 comment
Labels

Comments

@gubuntu
Copy link
Contributor

gubuntu commented Nov 22, 2018

problem

currently max seven concurrent analysis can run (each in their own celery worker). If you want to start another analysis in that situation then you either have to wait for one to finish or cancel one.

However, a user would have no way of knowing this.

solution

communicate to the user if this situation arises as well as what they can do about it

@gubuntu
Copy link
Contributor Author

gubuntu commented Nov 23, 2018

from @lucernae in Slack:

But it would make sense later if GeoSAFE automatically limit maximum concurrent jobs based on total scale that we used. It’s just that, we don’t have a way for GeoSAFE to automatically know that limit yet. It had to be set manually if we want to implement it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants