Red Hat Bugzilla – Bug 1017996
Scaling not choosing random hosts
Last modified: 2017-05-31 14:22:11 EDT
Description of problem:
After change scaling limits the broker create all gears on the same node on a district with 3 nodes
Version-Release number of selected component (if applicable):
Create a district with 3 nodes
Create a scaled app
Change scaling limits to --min 3 --max 6
Almost all gears are running on unique node
The gears should be distributed and the node with less gears running should be used
I tried this on a 2-node setup and it worked. The new gears were shared between the nodes. Selecting a node to host a gear also depends on the active capacity of the node, among other factors.
If this still does not work for your specific use case, you now have the ability to provide your own implementation. We recently introduced the feature to allow admins to provide their own node selection algorithm by implementing the plugin. Refer origin-server/controller/lib/openshift/application_container_proxy.rb for more details. Also take a look at the test case --> origin-server/broker/test/functional/node_selection_plugin_test.rb
Thank you for your comments, this is a very old bug and was filled on Origin Release 2.
Checked with devenv_5760, and can not reproduce this issue.
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.