We’ll be performing maintenance on our database servers starting at 15:00 UTC on Thursday, February 20th. It’ll take about 15 minutes to transfer services from our primary database server to our standby, after which normal service will resume. Thanks for your patience during this time.
Category: Hosting
Welcome Julian45 (and atj)!
I’m pleased to announce that Julian Anderson (julian45) and Adam James (atj) have joined our team as volunteer System Administrators. Julian has just now joined the team, where as Adam has been part of it for nearly 2 years and I failed to post the requisite blog post welcoming him. Mea culpa, Adam! Welcome to both of you!
We welcome volunteers to help us with our infrastructure, which continues to grow and become more complicated. The ListenBrainz project in particular has many moving parts in order to process the user’s data (stats, recommendations, fresh releases, etc.). On top of that, we’re working hard to make sure that our infrastructure is as automated as possible, so we welcome any help from people who know Ansible, like Julian and Adam.
Continue reading “Welcome Julian45 (and atj)!”Downtime today for PostgreSQL / MusicBrainz schema change upgrade: 17:00 UTC (10am PT, 1pm ET, 7pm CEST)
Today (Monday, May 13) at 17:00 UTC (10am PT, 1pm ET, 7:00pm CEST), we’ll be:
- Upgrading our production database server to PostgreSQL v16.
- Performing the MusicBrainz schema change upgrade.
See the previous announcement on this topic for more information.
Expect MusicBrainz and services that depend on its database (MetaBrainz, ListenBrainz, the Cover Art Archive, CritiqueBrainz, BookBrainz) to be down for the hour, but we’ll be working to restore services as quickly as possible.
Afterward, we’ll post instructions here on how to upgrade your MusicBrainz mirror server (whether using musicbrainz-docker or otherwise).
P.S. The initially announced upgrades for MusicBrainz search engine are just about to reach our beta website, and thus are postponed for mirrors too.
ListenBrainz service incident
Hello!
I’m sad to report that we had an incident on one of the ListenBrainz production database servers, where someone on our team might have accidentally run our test suite on our production server.
Planned downtime for Monday, October 23, 15:00 UTC
We’ll be performing maintenance on our database servers starting at 15:00 UTC tomorrow, October 23. It’ll take about 15 minutes to transfer services from our primary database server to our standby, after which normal service will resume. Thanks for your patience during this time.
Planned downtime for Monday, May 29, 15:00 UTC
We’ll be performing maintenance on our database servers starting at 15:00 UTC today, May 29. It’ll take about 15 minutes to transfer services from our primary database server to our standby, after which normal service will resume. Thanks for your patience during this time.
Planned downtime for Thursday, February 2, 15:00 UTC
We’ll be performing maintenance on our primary database starting at 15:00 UTC on February 2. It’ll take about 20 minutes to transfer services from our primary database server to our standby, after which normal service will resume. Thanks for your patience during this time.
Planned downtime for Thursday, April 14, 16:00 UTC
We’ll be taking all services down tomorrow, April 14, at 16:00 UTC (11 am CDT, 9 am PDT, 6 pm CEST) in order to reboot our primary database server. Downtime should be 10-15 minutes in duration. As usual, thanks for your patience!
Planned downtime for Wednesday, March 29, 16:00 UTC
We’ll be resuming maintenance on our database servers starting tomorrow, March 29, at 16:00 UTC. Like the previous downtime on March 2, we’ll need about 15 minutes to transfer services from our primary database server to our standby. Thanks again for your patience.
Planned downtime for Wednesday, March 2, 16:00 UTC
We’ll be performing some critical maintenance on our database server starting at 16:00 UTC on March 2. Some brief downtime (hopefully less than 15 minutes) will be required to transfer services from our primary database server to our standby, which will allow us to upgrade the primary’s system and perform hardware checks. Thanks for your patience during this time.
MetaBrainz Blog 