Closed Bug 524643 Opened 16 years ago Closed 16 years ago

Re-shuffle slaves between production-masters to match load

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: joduinn, Assigned: nthomas)

Details

Can we move some slaves from production-master02 over to production-master to keep up with the load there? Yesterday, production-master saw c4 times the volume of checkins that were on production-master02. Even though we'll end up shuffling them back again at some later time, this seems like a useful stopgap thing to do to keep down wait times.
John, is this still wanted/needed?
(In reply to comment #1) > John, is this still wanted/needed? Yes, please. The "wait times" report for yesterday (monday 2nd nov) showed production-master02 had ~12 jobs and no wait times while production-master had ~110 jobs, and up to 45min wait times. Not sure how many slaves would be appropriate to move - maybe something we can all bikeshed about in irc? :-)
Let's move the following from pm02 back to pm: moz2-darwin9-slave17 moz2-linux-slave22-25 moz2-win32-slave32-34
I'll get this prior to cleaning up slaves for 3.6b2.
Assignee: nobody → nthomas
Status: NEW → ASSIGNED
Priority: -- → P2
moz2-linux-slave22 is finishing it's last pm02 job and will reconnect to pm on reboot. Others all connected to pm already. Cleaned release directories at the same time.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Priority: P2 → --
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.