545900 - shuffle slaves

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

We need to shuffle slaves around again.  To figure out where slaves should go, we are going to aim to have the same percentage of idle/build from /buildslaves on each master.

Comment 1

[John Ford [:jhford] CET/CEST Berlin Time]

$ curl production-master.build.mozilla.org:8010/buildslaves 2> /dev/null | grep idle | wc -l
      64
$ curl production-master.build.mozilla.org:8010/buildslaves 2> /dev/null | grep building | wc -l
      34
$ curl production-master02.build.mozilla.org:8010/buildslaves 2> /dev/null | grep idle | wc -l
      50
$ curl production-master02.build.mozilla.org:8010/buildslaves 2> /dev/null | grep building | wc -l
       3
$

Comment 2

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

followup after irc, not sure if % is right metric. 

As of a few mins ago, production-master has 98 slaves (64 idle, 34 building)
and production-master02 has 52 slaves (50 idle, 3 building). Yet, pm02 is the
one reporting longer wait times earlier this week. Maybe making the two pools similar sizes might be better?

Comment 3

[John Ford [:jhford] CET/CEST Berlin Time]

We ended up deciding that n900 work was higher priority than moving slaves around.  Please file a new bug if we decide to shuffle slaves around in the near future.