Closed Bug 734393 Opened 12 years ago Closed 12 years ago

Evenly distribute tegras across masters

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

x86
Linux

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: Callek)

References

Details

(Whiteboard: [mobile][capacity])

The load on bm19 and bm20 is high (from checking ganglia) while bm22 has no slaves connected to it.

If one of those two masters go down we will have half of our tegras up.
This will take manual editing of buildbot.tac files and a restart of the affected tegra buildslaves.
Is there a way to easily shut down all of the CP instances on a foopy?
I know I could have a for loop calling stop_cp.sh for each tegra.

Would that work? or is there an easier way that you know?
Blocks: 711725
I will be doing this on Monday.
Assignee: nobody → armenzg
Priority: -- → P1
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #3)
> I will be doing this on Monday.

stop_cp.sh will do that by default if you don't give it a parameter IIRC
I will know in few days when I can get to this and adjust back the priority to P2 when working on it. P3 means I am not touching it and might be grabbing it back in 2 weeks.
Priority: P1 → P3
OS: Mac OS X → Linux
Whiteboard: [buildduty] → [mobile][capacity]
I believe Callek/bear already this did from looking at:
http://buildbot-master22.build.mtv1.mozilla.com:8201/buildslaves?no_builders=1
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
yep was done this week. was holding off on resolving until things look(ed) stable enough to leave it be. It is certainly that way now.
Assignee: armenzg → bugspam.Callek
Blocks: 817024
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.