Monthly Archives: July 2008

Maintenance for MySQL50-2 on EY01

Maintenance is over for MySQL50-2 on EY01 and was successful, all applications should be up and running. Let us know is you are seeing any issues at all.

Maintenance for MySQL50-2 on EY01

The database has been restarted, we are restarting applications now.

Maintenance for MySQL50-2 on EY01

We are beginning the scheduled maintenance on MySQL50-2 on EY01 now, database service will be unavailable during this maintenance.

ey02 service restored

We’ve brought back all affected ey02 slices, and it appears that the cause was the same as the earlier ey01 problems (cluster lock manager crashes).

If you are still seeing problems with any slices on ey02, please lodge a ticket or call our support line (+1-866-518-9275).

ey02 slice problems

There are currently a few slices on ey02 that are suffering similar symptoms to those shown on ey01 a little while ago.  We’re currently bringing them back to life.

ey01 service restored

We’ve brought back all affected ey01 slices and no more are falling over at the moment.  Initial investigations appear to point to the cluster lock manager being at fault, but we’ll continue our research to try and confirm that diagnosis.

If you are still seeing problems with any slices on ey01, please lodge a ticket or call our support line (+1-866-518-9275).

Service problems on ey01

A number of slices on ey01 are currently having some difficulties staying up.  We’re currently trying to resuscitate the effected slices, and work out what is causing the difficulties.  We’ll update the blog further once we’ve got some more info.

mysql50-9 resolved

We have now marked this issue as resolved.

If you are still experiencing any issues please open a ticket and we’ll follow it up.

mysql50-9 ey03 update #1

We have stopped a bunch of rogue queries that were taking up the database resources.

We are now waiting for it to calm down.

mysql50-9-master ey03

We are currently experiencing an issue on mysql50-9-master.

Our engineers are currently investigating the issue.

We apologise for any downtime.