Thursday, December 8, 2011

Amazon reboot causes a tempest on Twitter

(gigaom.com) -- Amazon is planning to reboot an undetermined number of customer EC2 instances in the coming week or so, something that caused a stir among Amazon watchers today.

Randy Bias, CTO and founder of Cloudscaling, a big user of Amazon services, first reported what appeared to be the scheduled reboot of ”hundreds to thousands” of EC2 instances early Wednesday afternoon.

More from gigaom.com
  • A database to help the military share its airwaves
  • 955 Dreams tackles music discovery with Band of the Day
  • 10 ways to deal with cybersecurity in a smart grid world

A check of the Amazon dashboard at 3:45 p.m. EST showed operations running normally except in the Northern Virginia data center which reported “problems with ELB  scaling and provisioning” for the eastern U.S. region. ELB is elastic load balancing which distributes a users application load across multiple EC2 instances.

An Amazon spokeswoman said via email that EC2 services are running normally and that the reboots are scheduled and customers are informed of them in advance. The company upgrades the EC2 frequently, often in a way that is invisible to customers, but some updates require that instances be restarted, she said “That’s what you’re seeing discussed today as we’ve sent customers the schedule.&r! dquo;

Customers can also restart their instances earlier than the scheduled time if they prefer.

Bias published a redacted letterAmazon sent to a customer on December 6 with reboots slated to begin on December 15.

She did not give specifics of the patches, although some Amazon watchers think they may have to do with Xen hypervisor issues,

Photo courtesy of Flickr user  liber.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

  • Migrating media applications to the private cloud: best practices for businesses
  • Infrastructure Q3: OpenStack and flash step into the spotlight
  • NewNet Q2: Google closes the quarter with a bang

No comments:

Post a Comment