Closed
Bug 765929
Opened 13 years ago
Closed 13 years ago
Determine why auto-refresh was slow on socorro1.dev.db
Categories
(Data & BI Services Team :: DB: MySQL, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mpressman, Assigned: mpressman)
References
Details
The automated refresh usually takes an hour and a half. Last night at midnight I noticed that the job was only half way through completion. After noticing the load climbing, above 10.
| Assignee | ||
Updated•13 years ago
|
Assignee: server-ops-database → mpressman
| Assignee | ||
Comment 1•13 years ago
|
||
This was due to my mistake. Basically bad scripting. It had been suggested to add in running an rsync command to ensure that files are check summed on the destination machine. I was able to reproduce this by running the script on my vm and indeed found that after the initial copy the rsync kicked off and the nc command kicked off again. This caused both file and network io resources to spike and additionally cause a corruption as discovered in https://bugzilla.mozilla.org/show_bug.cgi?id=766153
| Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Data & BI Services Team
You need to log in
before you can comment on or make changes to this bug.
Description
•