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

Flintrock gets terribly slow if known_hosts is big #189

Open
douglaz opened this issue Feb 14, 2017 · 1 comment
Open

Flintrock gets terribly slow if known_hosts is big #189

douglaz opened this issue Feb 14, 2017 · 1 comment

Comments

@douglaz
Copy link
Contributor

douglaz commented Feb 14, 2017

  • Flintrock version: master
  • Python version: 3.4.3
  • OS: Ubuntu

So slow that it's unable to create a cluster with more than a couple of machines.

This seems to be a paramiko issue (paramiko/paramiko#191), must it's something flintrock's users and developers should be aware.

Perhaps there is a workaround for that? At least a warning would be helpful to avoid lots of wasted hours trying to figure out why flintrock is behaving so weird in an old machine.

@nchammas
Copy link
Owner

Hmm, I wonder if Flintrock even needs to read from known_hosts. If not, we can presumably just turn that off via an option to Paramiko.

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

No branches or pull requests

2 participants