SUMO stage and stage-new: sync database with production

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
--
critical
RESOLVED FIXED
8 years ago
3 years ago

People

(Reporter: paulc, Assigned: fox2mike)

Tracking

Details

(Reporter)

Description

8 years ago
It would be awesome if you could sync the support-stage and support-stage-new databases with production.

We need to test some database changes, and the more up-to-date the data, the better.

Thanks!
(Assignee)

Updated

8 years ago
Assignee: server-ops → shyam
(Assignee)

Comment 1

8 years ago
Why exactly is this critical?
Critical is the 8 hours for stage updates specified in the SLA. And it's blocking QA (by blocking another thing we'll file after it's done and we've double checked some data).
(Assignee)

Comment 3

8 years ago
Haha, I could have sworn I've read the SLA and didn't see anything about stage, but James is right and I stand pwned ;)

Will keep you guys posted and it'll be done within 8 hours ;)
The 8 hours means 8 hours pacific time (normal business hours, 9-5), fyi. :)
(In reply to comment #4)
> The 8 hours means 8 hours pacific time (normal business hours, 9-5), fyi. :)

I know. Of course Shyam is in Singapore, which is convenient in this case. ;)

Anyway, he just asked why it was critical; I answered.
(Assignee)

Comment 6

8 years ago
[root@tm-stage01-master01 ~]# time (zcat support_mozilla_com.2010.04.15.sql.gz | mysql --max_allowed_packet=1G support_wiki)

real    21m53.704s
user    2m59.322s
sys     0m12.270s

[root@tm-stage01-master01 ~]# time (zcat support_mozilla_com.2010.04.15.sql.gz | mysql --max_allowed_packet=1G support_stage_new_mozilla_com)

real    23m21.198s
user    2m58.591s
sys     0m12.622s

Done.
Status: NEW → RESOLVED
Last Resolved: 8 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.