jamesheroku
Joined 18 years ago
Karma
1,071
Submissions
33
Member since
Jan 12
Founder, Heroku + Heavybit - the leading fund for developer companies. http://heavybit.com
View on Hacker NewsRecent submissions
Comment · 16 years ago
Heroku IPs are 75.101.163.44, 75.101.145.87, and 174.129.212.2, if you want to update the script to make the distinction from raw Amazon EC2.
Comment · 16 years ago
18 now. ;-)
Comment · 16 years ago
For sub-hour scheduled or recurring tasks, most users prefer a scheduled background task with DJ, rather than old-school cron. There are a bunch of ways to do this, for example:
Delayed::Job.enqueue(work, 0, Time.now + 5.minutes)
Comment · 17 years ago
This article contains quite a bit of inaccurate information.
Despite the size of 22 double-XL instances, they were a small portion of our overall footprint in EC2; it takes well over that kind of capacity to run the platform.
Those instance types all happened to be in one availability zone for a variety of reasons. Our platform overall does not live in a single zone.
Losing machines is not a problem for us (we cycle them constantly, in fact). Normally losing even that many machines would not even be noticed by our customers; this was an unusual case in which several factors cascaded into a larger problem.
To be clear, this downtime (45 minutes or so, with full normal state by 90 minutes) was, unfortunately, our fault - not Amazon's. EC2 instances vaporizing is an expected part of using the service.
We've made a couple of operational changes that will prevent these issues in the future, and we sincerely apologize to any customers who were affected.