Having a third server would mean that we can use both current servers as active. We could move some dumps jobs off onto the current fallback host, namely everything but the xml/sql dumps. This will mean some network and i/o load relief for the one active server now, the ability to swap in the new server for either in case of hw failure, and seperate maintenance windows for xml/sql dumps hosts vs misc cron hosts for e.g. security reboots.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| enable rsync to dumpsdata1003 for all dumps servers | operations/puppet | production | +2 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | MoritzMuehlenhoff | T224549 Track remaining jessie systems in production | |||
| Resolved | ArielGlenn | T224563 Migrate dumpsdata hosts to Stretch/Buster | |||
| Resolved | ArielGlenn | T219768 Get a third dumpsdata server | |||
| Unknown Object (Task) | |||||
| Resolved | ArielGlenn | T234076 (Need by Aug 1) rack/setup/install dumpsdata1003.eqiad.wmnet |
Event Timeline
Comment Actions
I've asked for that in the budget for next year. @mark, please comment when we have updates.
Comment Actions
I'm going to go ahead with this; @RobH, I need a quote for a host that looks like dumpsdata1001/2. Previous quote info is here: T161344 and specs are here: https://wikitech.wikimedia.org/wiki/Dumps/Dumpsdata_hosts#Hardware What else do you need from me to proceed? (If I should create a separate task for a different queue and tag it with a specific team, just lmk that too.)
Comment Actions
I guess by the closure of the subtask that the server has arrived? What's the outlook for getting it racked?
Comment Actions
Change 550090 had a related patch set uploaded (by ArielGlenn; owner: ArielGlenn):
[operations/puppet@production] enable rsync to dumpsdata1003 for all dumps servers
Comment Actions
Change 550090 merged by ArielGlenn:
[operations/puppet@production] enable rsync to dumpsdata1003 for all dumps servers