Server upgrade and schema change, 2014-05-14

Hello again! This fortnight, as we’ve mentioned among the past few posts, is our twice-annual schema change release! This means that we’ve got some big changes, as well as special upgrade instructions.

In the former category, we’ve added support for two new entities: Series and Instruments, each of which is exactly what it sounds like. We’ve also done some various cleanup (tables missing from replication, making some attribute-style tables (e.g., label types) trees, and more properly orderable, removing unuseful sortnames). In non-schema-change fixes, we’ve fixed some merging for Artist Credits, show Area names after Places routinely, and perhaps most excitingly, added smaller versions of the relationship editor for other entities. It’s now possible to add relationships to any entity from most entity edit pages, expanding on our previous addition of URL editing!

As far as upgrading:

Ensure you’ve replicated up to the most recent replication packet available with the old schema. (if you’re not sure, run ./admin/replication/LoadReplicationChanges and see what it tells you).

Take down the web server running MusicBrainz, if you’re running a web server.

Turn off cron jobs if you are automatically updating the database via cron jobs.

Make sure your REPLICATION_TYPE setting is RT_SLAVE

Switch to the new code with git fetch origin followed by git checkout v-2014-05-14-schema-change

5 thoughts on “Server upgrade and schema change, 2014-05-14”

Hi,
I know this might sound like a lame question, but how do I “Take down the web server running MusicBrainz”?
Believe it or not, but I’ve spent an hour trying to figure it out and nothing. When I kill the ‘app.psgi’ or ‘plackup’ processes they keep coming back.

Also, thanks for the instructions, Tomasz! I couldn’t figure out how to shut down the plackup web server either.

In the end, though, I was too lazy to use your workaround. I decided to just proceed without fully taking down the web server – and so far, it seems like it worked out fine. I think everything is updated now, since replication beyond 5/14/2014 is working in my MusicBrainz mirror VM now.

The one part of the web server I did figure out how to shut down was Jetty. I used this command for that: