Socorro:Releases/18: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
This database upgrade involves a number of irreversable changes. As such, two additional steps are required before deploying it: | This database upgrade involves a number of irreversable changes. As such, two additional steps are required before deploying it: | ||
# Archival final "pre-mobeta" offsite backup. | # Archival final "pre-mobeta" offsite backup. See bug: https://bugzilla.mozilla.org/show_bug.cgi?id=762305 | ||
# Disable replication to master02 before running the upgrade, and do not restore it until after QA verification. This may then require a full resync of master02. | # Disable replication to master02 before running the upgrade, and do not restore it until after QA verification. This may then require a full resync of master02. | ||
Revision as of 19:45, 22 August 2012
Upgrade Steps
This upgrade requires a downtime. Likely the downtime will only be 1/2 hour, but we should schedule a 1-hour downtime just in case. Both the processors and the web UI should be down during the upgrade.
Database changes need to be deployed first, then UI/mware changes.
Database Upgrade
As usual, run "18.0/upgrade.sh breakpad".
This database upgrade takes around 1/2 hour to run, assuming a 2-week backfill of the new matviews. Should we decide to do more than 2 weeks of backfill, this can be adjusted by editing upgrade.sh.
This database upgrade is lock-sensitive. As such, it requires the downtime per above.
This database upgrade involves a number of irreversable changes. As such, two additional steps are required before deploying it:
- Archival final "pre-mobeta" offsite backup. See bug: https://bugzilla.mozilla.org/show_bug.cgi?id=762305
- Disable replication to master02 before running the upgrade, and do not restore it until after QA verification. This may then require a full resync of master02.