Description of problem: When an application is scaled up, the gears are not evenly distributed across nodes in the district or zone. Version-Release number of selected component (if applicable): 2.2.5 How reproducible: Always Steps to Reproduce: 1. With 4 nodes, create a single district under one region with two zones (two nodes per zone) 2. Create a scaled application in this district. 3. Make the application HA 4. Scale the application to a high number of gears 5. Use `oo-admin-ctl-gears list | wc -l` on each node Actual results: (After scaling to 80 gears) node1 (zone1): 11 node2 (zone1): 17 node3 (zone2): 14 node4 (zone2): 38 zone1: 28 zone2: 52 Expected results: node1 (zone1): 20 node2 (zone1): 20 node3 (zone2): 20 node4 (zone2): 20 zone1: 40 zone2: 40 Additional info: If zones are not present, the gears are distributed similarly across the district.
https://github.com/openshift/origin-server/pull/6160
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/99d3dcc1dba1c5a1b7f28ecffff7fe65923f6a5b Ignore least preferred servers if all servers are least preferred Bug 1228373 Bug link https://bugzilla.redhat.com/show_bug.cgi?id=1228373 If an application is already scaled out so that it has a gear on all available nodes, all nodes will be considered 'least_preferred_servers'. This will cause only one server to be returned from rpc_find_all_available, giving select_best_fit_node only one server to choose. This caused sparatic and uneven gear placement from highly scaled applications. This fix will ignore the least_preferred_servers list if all available servers are included in the list.
The commit pushed only partially resolves the issue. Distribution is better, but not even as expected. A complete fix is being investigated in online bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1234603
There is no fixed package in the puddle After installation, QE check the issue [root@broker ~]# oo-admin-ctl-gears list|wc -l 15 [root@node1 ~]# oo-admin-ctl-gears list|wc -l 16 [root@node2 ~]# oo-admin-ctl-gears list|wc -l 8 [root@node3 ~]# oo-admin-ctl-gears list |wc -l 21 QE check the installed package. #rpm -qa|grep rubygem-openshift-origin-controller rubygem-openshift-origin-controller-1.36.2.3-1.el6op.noarch # rpm -qa|grep rubygem-openshift-origin-msg-broker-mcollective rubygem-openshift-origin-msg-broker-mcollective-1.34.1.1-1.el6op.noarch There is no fixed package in the puddle.
Check on puddle [2.2.7/2015-09.21.1] After installation, QE check the issue [root@broker ~]# oo-admin-ctl-gears list | wc -l 20 [root@node1 ~]# oo-admin-ctl-gears list | wc -l 20 [root@node2 ~]# oo-admin-ctl-gears list | wc -l 20 [root@node3 ~]# oo-admin-ctl-gears list | wc -l 20 Move this issue to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1844.html