Closed
Bug 997702
Opened 10 years ago
Closed 10 years ago
git1 memory
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: fubar, Unassigned)
References
Details
git1.dmz.scl3 is running into OOM issues and burning trees nightly. It's a BL460C G7 blade, and docs say it'll take up to 48GB memory; it's currently got 36. Do we have spare memory around to upgrade it? (Enough to upgrade it and git2, it's warm standby?)
Updated•10 years ago
|
colo-trip: --- → scl3
Comment 1•10 years ago
|
||
:fubar, we have enough spare memory on site to bump each of these hosts up an additional 8gb, will that help?
Reporter | ||
Comment 2•10 years ago
|
||
Since this will cause an outage, and other changes have made the immediate pain go away, we're going to defer this. Once we get n+1 servers up, we may well put in an order for more ram. Thanks!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Comment 3•10 years ago
|
||
just a heads up, we were able to allocate some more dimms into the spare pool after the spring clean up so we can bump these up to 48gb if needed.
Resolution: INVALID → FIXED
Comment 4•10 years ago
|
||
Wontfix seems like the correct resolution given comment 2 and comment 3?
Resolution: FIXED → WONTFIX
Comment 5•10 years ago
|
||
We need to reconsider this, as the prior bandaids are starting to leak. :/
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 6•10 years ago
|
||
worked with :fubar to upgrade these nodes to 64gb.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•