You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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.
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:
[ ] Add the ability to only reconcile added/deleted nodes instead of run rke on all nodes.Moved to Refactor reconcile to be done on added/deleted nodes instead of all nodes #974This should be part of the rke optimization and refactoring issue rancher/rancher#15975
The text was updated successfully, but these errors were encountered: