Closed Bug 477183 Opened 15 years ago Closed 15 years ago

Add additional database slaves for AMO, Bouncer, and Bugzilla

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mrz, Assigned: justdave)

References

()

Details

(Whiteboard: ETA 05/26)

During release periods, bouncer needs at least two databases to handle load.  Need to add a third to be able to withstand a failure of any one during release.
got hardware for me?
We need additional slaves for AMO and Bugzilla, as well.  I have the designated hot spares assigned to those two right now, and I'd like to have spares available for emergencies again.
Summary: Add third database for bouncer db → Add additional database slaves for AMO, Bouncer, and Bugzilla
I've snagged the former mrdb05 box for the new AMO slave, since it's the same type of hardware the rest of the AMO slaves are using.  None of the other free hardware we have at the moment is appropriate for the other two though.  Supposedly we have some new blades getting racked any day now, I'll wait for those.
Whiteboard: waiting on hardware
FYI, just discovered the existing Bugzilla slave has 16 GB of RAM (and is actually using it, 14GB physical in use at the moment - the temporary box I have helping out in that pool right now only has 8 and it's swapping).  So we'll need to make sure we have that much available in one of the boxes for that.
This is now blocker status until the new bouncer slave is up.  This one in particular must be done before the FF 3.0.7 release.  Getting the additional AMO slave up before the FF 3.0.7 release will be a bonus.
Severity: normal → blocker
Can you take one of these machines temporarily?  There are a couple there you could spin up in short order.
I have one allocated for bouncer already.  Was hoping for a couple of the new blades for AMO and Bugzilla.
Severity: blocker → normal
Severity: normal → blocker
Hmm, I take that back, AMO is the one I already had hardware for.  I need one for bouncer still.  I'll snag one of those blades for Bouncer.
tm-amo01-slave01 and tm-bouncer01-slave03 are now online.  The bouncer slave is on crummy hardware, but it'll survive for now. :)
Severity: blocker → normal
Just to clarify (since someone asked), by "crummy" I meant non-redundant.  It's using one of the blades from the test lab chassis that doesn't have redundant power supplies/NICs/etc.  It's otherwise got the usual slate of processor and RAM so it should keep up just fine.  Considering that it's in a pool with other mostly-identical slaves anyway, that probably doesn't really matter.
oh, we're better off than I thought it was...

20:27:48 < mrz> hey dave, the BL260c vs. the BL460c - the 260 is sata
20:27:50 < mrz> only difference
20:28:12 < mrz> the chassis it's in, however, differs from the c7000 chassis in
                that it has only one pass-through module and is an 8 bay chassis
                vs. 16
20:28:19 < mrz> but fully redundant power
Phong is going to check inventory to see if we have memory in stock.
We have 1 pack of 2x2GB.  Go ahead and order 12 GB more.
What do you need for AMO & bouncer?
Whiteboard: waiting on hardware
(In reply to comment #15)
> What do you need for AMO & bouncer?

Nothing, unless you want to get the tm-bouncer01-slave03 off the test lab chassis.
I do.  That's lab hardware, not meant to be long term production.

Take https://inventory.mozilla.org/systems/show/965 (and rename if needed).
I forgot to mention the second Bugzilla slave is up and in the slave pool as of Thursday or Friday last week.  Haven't moved bouncer01-slave03 to the new hardware yet.
Whiteboard: waiting on bouncer01-slave03
Whiteboard: waiting on bouncer01-slave03 → ETA 05/26
ok, bouncer01-slave03 has been moved.  This is done. :)
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.