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

Master is put on a huge instance when you need a huge slave #284

Closed
pferrel opened this issue Jan 10, 2019 · 1 comment
Closed

Master is put on a huge instance when you need a huge slave #284

pferrel opened this issue Jan 10, 2019 · 1 comment

Comments

@pferrel
Copy link

pferrel commented Jan 10, 2019

  • Flintrock version: 0.11.0
  • Python version: 3.7
  • OS: macOS Mojave

It seem like there is only one instance size so the master is started on what can often be a huge instance. If you need a huge slave, the master gets the same instance even though the master does very little and needs only a tiny instance.

Is there any way around this?

@nchammas
Copy link
Owner

Duplicate of #199.

Not sure if there is a workaround available. You can try launching a cluster with 1 instance type and then adding new slaves with a different instance type, but I don't know if Flintrock currently allows that.

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