I agree entirely.
The messaging needs to have a very strong correlation to reality. If
elevated error rates describes a specific thing, we should know exactly
what that is. If it covers a range of issues, then the message is
insufficient.
And, of course, Eric's point about what elevated could
I think that when there is general AWS instability affecting Heroku, the
default error message might provide a word or two that attributes the issue
to Heroku's responsibility.
When a customer sees the attached, it would be nice to have some cover.
--
You received this message because you are
Here's what you want -- from: http://status.aws.amazon.com/
The last three provide the most information.
1:41 AM PDT We are currently investigating latency and error rates with EBS
volumes and connectivity issues reaching EC2 instances in the US-EAST-1
region.
2:18 AM PDT We can confirm
Exactly. Me, too.
So I think Heroku needs to help us slobs out and take credit for this outage
with an error page that says: Amazon done it.
On Thu, Apr 21, 2011 at 2:19 PM, chris mcclellan...@gmail.com wrote:
We created a custom error page and are seeing the heroku generic instead of
our
You had 1666+ requests/second, and had to bring in several hundred
more EC2 instances?
Those numbers seem off.
On Thu, Feb 3, 2011 at 8:08 AM, Neil Middleton neil.middle...@gmail.com wrote:
This week in the UK we had the launch of police.uk, an Django based site
hosted on EC2. Pretty much
:
Not us, someone else.
From what I gather, at 7am they were doing ~5m hits per hour.
On Feb 3, 2011 8:26 PM, John Norman j...@7fff.com wrote:
You had 1666+ requests/second, and had to bring in several hundred
more EC2 instances?
Those numbers seem off.
On Thu, Feb 3, 2011 at 8:08 AM, Neil
Brandon: Regretably, I'm cheating and am using the Dalli gem without the
guidance of Heroku. :-( I couldn't get memcached-northscale to compile on my
Mac. Whatever.
In any case:
Rails.cache.write foo, bar
= true
Rails.cache.read foo
= bar
Rails.cache.read foo
= bar
Rails.cache.read foo
= bar
P.S. Stack = bamboo-mri-1.9.2, Rails 3.0.0.
On Tue, Oct 5, 2010 at 8:13 AM, John Norman j...@7fff.com wrote:
Brandon: Regretably, I'm cheating and am using the Dalli gem without the
guidance of Heroku. :-( I couldn't get memcached-northscale to compile on my
Mac. Whatever.
In any case
a recognizable negative impact.
On Tue, Oct 5, 2010 at 9:13 AM, John Norman j...@7fff.com wrote:
Brandon: Regretably, I'm cheating and am using the Dalli gem without the
guidance of Heroku. :-( I couldn't get memcached-northscale to compile on my
Mac. Whatever.
In any case:
Rails.cache.write foo
I've been noticing slow performance when returning an HTTP 201 (Created). I
can't isolate it in the Rails request cycle.
The response from Heroku is not GZIP'ed (though I don't think that's the
whole problem), and the cache headers are different than for a 200.
I switched the response status to
This would seem to be my problem with the 201 (same as :created) I reported
earlier.
Thanks!
On Wed, Sep 29, 2010 at 5:53 PM, Jacob Vorreuter
jacob.vorreu...@gmail.comwrote:
Your problem is being caused by a missing Content-Length header in the
HTTP response:
$ curl -v -d
Hi. I've been getting some auth errors from SendGrid. Anyone else?
Seems to be intermittent. I'm not over quota.
John
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from
Ah.
Currently experiencing a database issue that is causing website errors
working on resolution. #status http://twitter.com/search?q=%23status
http://twitter.com/sendgrid
On Mon, Sep 27, 2010 at 1:03 PM, John Norman j...@7fff.com wrote:
Hi. I've been getting some auth errors from SendGrid
Well, you should get an e-mail if your app is generating backlogs.
I have one app that did generate 2 in a whole week, and I received at least
two e-mails from Heroku suggesting that I up the number of dynos.
On Fri, Sep 24, 2010 at 11:42 AM, mattsly matt...@gmail.com wrote:
How are you
My delayed jobs (bamboo-ree-1.8.7) are working, too.
On Wed, Aug 18, 2010 at 7:06 PM, chris mcclellan...@gmail.com wrote:
Jobs on our apps all seem to be executed properly by a worker. Try
running heroku rake jobs:work and see if it blows up w/ a backtrace or
not.
I was running into a
15 matches
Mail list logo
