The cause of the outage is the below incident, which I've copied from AWS Status. This EBS had our database storage on it, and the drop in performance broke everything. The long outage was due to moving the database storage to a different backend storage system and bringing things back online. We do not currently have the ability to run multiple redundant database servers in multiple AZ's to protect against this sort of issue, this is something we are doing for later this year.
> > 11:38 AM PST We are investigating degraded performance for a small > number of EBS volumes in a single AZ in the EU-WEST-1 region. > 12:07 PM PST We are continuing to investigate degraded performance for > a small number of EBS volumes in a single AZ in the EU-WEST-1 region. A > small number of newly launched EBS-backed instances may also fail to > reach the 'running' state. > 12:38 PM PST Between 11:27 AM PST and 12:14 PM PST a small number of > EBS volumes in a single AZ in the EU-WEST-1 region experienced degraded > performance. Additionally, a small number of newly launched EBS-backed > instances failed to reach the running state. The issue has been > resolved and the service is operating normally. > -- andyg ------------------------------------------------------------------------ andyg's Profile: http://forums.slimdevices.com/member.php?userid=3292 View this thread: http://forums.slimdevices.com/showthread.php?t=93914 _______________________________________________ squeezenetwork mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezenetwork
