Coincidence. I've noticed a surge in mail timeouts over the past few days. As I said on a different thread, this is really stupid - google should be able to send mail without EVER having a timeout. For now, you need to always send mail from a task, because of these ridiculous exceptions.
On Sep 13, 2011, at 3:44 PM, Rishi Arora wrote: > I received at least 10 instances of these errors in one day yesterday, out of > around ~50 emails that were sent through the day. In the last few months > that my app has been executing, I have never seen this. Searching on Google > revealed that the best cure is to send emails in the context of a task-queue > request instead of a user facing request. That makes sense. However, > yesterday was also the day I rolled out instance-hour-saving optimizations, > and reduced my max_idle_instances to 1, while setting min_pending_latency to > 200ms. This scheduler parameter change has not had any effect on overall > performance of my app, in terms of average latencies, etc. I'm wondering if > it is just a coincidence that my mail.send() call timedout, or was it somehow > related to my scheduler parameter changes. Any thoughts? > > Thanks in advance. > Rishi > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
