2013-10-14 schema change release update instructions

As promised, here are the instructions for updating any instances of MusicBrainz you might have. You will need to perform these steps to upgrade to the new version:

  1. Take down the web server running MusicBrainz, if you’re running a web server.
  2. Turn off cron jobs if you are automatically updating the database via cron jobs.
  3. Make sure your REPLICATION_TYPE setting is RT_SLAVE
  4. Switch to the new code with git fetch origin followed by git checkout v-2013-10-14
  5. Run carton exec -Ilib — ./upgrade.sh (or simply ./upgrade.sh if you aren’t using carton, such as for VM users or fairly new installs).
  6. Set DB_SCHEMA_SEQUENCE to 19 in lib/DBDefs.pm
  7. Turn cron jobs back on, if needed.
  8. Restart the MusicBrainz web server, if needed.

If your server fails to start or cron is having issues, it may be a missing perl module problem. To check for any missing perl modules, follow the instructions in INSTALL.md.

6 thoughts on “2013-10-14 schema change release update instructions”

  1. Thank you for the update and this instructions. If ‘git fetch origin’ displays two lines:

    * [neue Markierung] v-2013-10-14 -> v-2013-10-14
    Von git://github.com/metabrainz/musicbrainz-server
    * [neue Markierung] v-2013-09-30 -> v-2013-09-30

    do I have to checkout both entries or only the newest one?

  2. I only checked out the newest one v-2013-10-14, ran
    carton exec -Ilib — ./upgrade.sh
    and about 83 minutes later, my Virtual Machine/Ubuntu 12.04 LTS says:

    Die Okt 15 11:46:53 CEST 2013 : DROP TABLE puid;
    Die Okt 15 11:47:00 CEST 2013 : Remove _name tables and regenerate name columns
    Die Okt 15 12:43:34 CEST 2013 : Creating the Place entity
    Die Okt 15 12:43:57 CEST 2013 : Updating musicbrainz schema sequence values
    Die Okt 15 12:44:11 CEST 2013 : Mark deleted editors more accurately
    Die Okt 15 12:44:26 CEST 2013 : Adding ended columns for alias
    Die Okt 15 12:44:32 CEST 2013 : Add disambiguation to areas
    Die Okt 15 12:44:35 CEST 2013 : Adding link_type.is_deprecated
    Die Okt 15 12:44:35 CEST 2013 : Creating views
    Die Okt 15 12:44:36 CEST 2013 : Going to schema sequence 19
    UPDATE 1
    Die Okt 15 12:44:37 CEST 2013 : Vacuuming DB.
    Die Okt 15 13:09:02 CEST 2013 : Done
    Die Okt 15 13:09:02 CEST 2013 : UPDATE THE DB_SCHEMA_SEQUENCE IN DBDefs.pm TO 19 !

    The replication is running fine with schema 19.

    The own Search Server still runs on a older code base, because I don’t know exactly how to update it.

  3. Can you write these instructions in detail please? They make absolutely no sense to me at all!

    Clear simple instructions are essential so we don’t all end up in a mess every Schema Upgrade.

    Remember many of us using the virtual machine may not use linux regularly.

  4. Zag:

    Please don’t update the VM, its a total pain. Next week we will release a new VM based on the latest schema. We’re just waiting for the most critical fires to be put out.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.