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

Optimize rke to handle creation of more than 1000 nodes #953

Closed
4 tasks done
galal-hussein opened this issue Oct 11, 2018 · 4 comments
Closed
4 tasks done

Optimize rke to handle creation of more than 1000 nodes #953

galal-hussein opened this issue Oct 11, 2018 · 4 comments
Assignees
Labels
Milestone

Comments

@galal-hussein
Copy link
Contributor

galal-hussein commented Oct 11, 2018

Currently rke can be used with any number of nodes, however running on large number of nodes raises some issues including too many open socket files and slow of the process.

The following is a list of optimizations that can be implemented to speed up the process and handle this number of nodes:

This should be part of the rke optimization and refactoring issue rancher/rancher#15975

@moelsayed
Copy link
Contributor

Fixes done for this issue are mostly performance tweaks to handle large number of nodes. Several areas are changed internally, so the common use cases should be verified with the latest build.

Notable changes in UX:

  • The tunnel up phase is much faster now.
  • Sync labels and taints phase is faster and more stable with large number of nodes.
  • State save phase is much faster now.

@dnoland1
Copy link

@moelsayed Will these improvements also help rke remove? On a ~800 node cluster, it takes over 30 minutes.

@dnoland1
Copy link

My observation is rke remove is slow on large clusters and running tasks sequentially. Filed another issue to address - #981

@dnoland1
Copy link

Tested yesterday with a master server build - b324973 on an environment with 793 nodes. Total time for rke up to run was 13 minutes, 24 seconds. When using rke v 0.1.10, it took 35 minutes, 5 seconds on the same environment.

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

5 participants