status | alwaysdata

31 mars 2016 13:30	We’re investigating.
31 mars 2016 14:05	We’re still trying to understand why we’re having issues.
31 mars 2016 14:55	We don’t have an ETA yet, we’re still investigating.
31 mars 2016 15:09	We seem to have found a temporary workaround.
31 mars 2016 16:37	We’ll continue using the workaround for now and keep investigating for a more permanent fix.
1 avr. 2016 09:37	The workaround is not as effective as yesterday, we’re observing a higher system load than usual.
1 avr. 2016 10:55	We’re pretty sure the underlying issue is a MySQL bug. Upgrading to a major MySQL version with no prior notification to our clients is not something we want to do. We’re instead installing a new MySQL server (running MariaDB 10.1). Clients that want to migrate from mysql1 to this new server should contact us by opening a support ticket from their administration panel.
1 avr. 2016 13:45	The new MySQL server is ready, migrations will start shortly (for clients that opened a ticket).
1 avr. 2016 15:02	We’ve restarted mysql1 10 minutes ago, it’s been running smoothly since then, although we cannot explain why.
1 avr. 2016 17:29	mysql1 is still running fine. Migrations have been suspended for now as some databases refuse to get reimported and we’d like to find a proper solution until we resume the process.

Statut