The planned maintenance for mysql50-staging-1 on ey03 has been completed.
The maintenance on mysql50-staging-1 on ey02 has been postponed. This maintenance will be rescheduled when the issues have been resolved.
The planned maintenance for mysql50-staging-1 on ey03 has been completed.
The maintenance on mysql50-staging-1 on ey02 has been postponed. This maintenance will be rescheduled when the issues have been resolved.
The planned maintenance for mysql50-staging-1 on ey03 is still in progress. mysql50-staging-1-master has been restarted with a larger filesystem. All affected staging applications are now being restarted.
The planned maintenance for mysql50-staging-1 on ey03 is still in progress. mysql50-staging-1-replica has been restarted.
The maintenance for ey02 staging will be postponed due some issues on that cluster that will prevent the filesystem from being grown in a timely fashion.
The planned maintenance for mysql50-staging-1 on ey02 and ey03 is now in progress. This maintenance is being performed to grow the filesystems on both database servers.
The push went smoothly and no complications met.
We are pushing a low risk change to the ey02 gateways now.
The change has been pushed without issue as expected.
We are pushing a low risk change on the gateway on EY05 now.
Aside from EY01 MySQL50-4-master issue, all was well and quiet, the clusters were in good form and we experienced no failures. Have a great weekend!
A planned maintenance has been scheduled for 4:00AM PST on Saturday, February 28, in order to restart master and replica databases for mysql50-staging-1 on EY02 and EY03.
This restart is being performed in order to grow the data filesystems on both database servers to support the continued growth of staging environments. After this restart is completed, any impacted customer applications will be restarted. The total downtime is anticipated at 20 minutes, however the maintenance window is scheduled for an hour.