Closed
Bug 653539
Opened 13 years ago
Closed 13 years ago
move non-test slaves away from buildbot-master5 (and even shut off the build and try masters on it)
Categories
(Release Engineering :: General, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: armenzg)
References
Details
Currently buildbot-master5 is overloaded since it has more than 250 slaves connected to it. A simple pwd step can take more than 40 seconds on the slave. This means that test jobs are taking forever. For now we will temporarily move slaves from bm05 and try_master5 to other masters.
Assignee | ||
Comment 1•13 years ago
|
||
I have disabled bm6 & bm05-try on slavealloc (the previous names were from the Masters wiki page).
Assignee | ||
Comment 2•13 years ago
|
||
bm05-try was gracefully shutdown. bm6 has been marked to be gracefully shutdown but still has jobs running. bm04-tests1 is now being enabled in bug 607179 to help distribute the test slaves.
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•13 years ago
|
||
The load on buildbot-master5 is now sane since bm04-tests1 and bm06-tests1 have been enabled. We have now running on it: - bm6 - bm05-try - tm3 On slavealloc we have the following masters enabled: - bm6 - tm3 I will leave bm05-try disabled on slavealloc for now as I don't see the need to enable it (I am still watching migration to bm6).
Assignee | ||
Comment 4•13 years ago
|
||
buildbot-master5 looks good. Nothing left to be done.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•