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

Deprovision service bus on closing a cluster #136

Open
isaacabraham opened this issue Jan 21, 2016 · 2 comments
Open

Deprovision service bus on closing a cluster #136

isaacabraham opened this issue Jan 21, 2016 · 2 comments

Comments

@isaacabraham
Copy link
Contributor

I think that we should consider removing the service bus queue after deprovisioning a cluster. We're using the standard service bus package which has a cost associated with it without using it for anything. The cost is not massive to be fair - around 10eur a month but nonetheless someone can delete a cluster and be left with running costs anyway.

Any objection for me changing the management library to do this?

@eiriktsarpalis
Copy link
Member

This has already been implemented, but it is disabled by default. In principle, an mbrace cluster is a superset of any particular deployment; multiple deployments can be part of the same cluster either at the same time or successively. The nice thing about this is that computations can be suspended when no workers are running.

@isaacabraham
Copy link
Contributor Author

Yes. But we both know some people are particular about running costs of clusters - particularly if hidden. I know what you're saying about suspend / resume, but how often is that going to be happening? I would suggest that most people spin up a cluster and spin it down when they're done with it.

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

No branches or pull requests

2 participants