google-app-engine - Google App Engine - 等待太久未能尝试处理您的请求后，请求被中止

Question

我有时会遇到这个错误。

Request was aborted after waiting too long to attempt to service your request. Most likely, this indicates that you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/docs/quotas.html for more details.

导致它的请求有 10 秒的延迟和 0 毫秒的 cpu 时间。这是一个简单的 jsp 页面，根本不会做任何需要很长时间的事情。此外，我的应用的流量非常低，而且每次发生这种情况时，它都是唯一正在处理的请求。

这是什么原因造成的？

Answer 1

如果您的应用程序流量较低，则可能是启动时间。似乎有一个持续存在的问题，即启动实例需要很长时间，以至于它们违反了时间限制。

有些人通过每隔几分钟运行一次 cron/scheduled 请求来“解决”这个问题(尽管我个人认为这会适得其反，在某种程度上破坏了 Google 关闭您的应用程序的原因!)。

他们的 bugtracker 中有一个关于这个的问题:

http://code.google.com/p/googleappengine/issues/detail?id=2456

它现在被标记为 1.4 版已修复，这里有一些关于它的信息:

http://googleappengine.blogspot.com/2010/12/happy-holidays-from-app-engine-team-140.html

Always On - For high-priority applications with low or variable traffic, you can now reserve instances via App Engine's Always On feature. Always On is a premium feature costing $9 per month which reserves three instances of your application, never turning them off, even if the application has no traffic. This mitigates the impact of loading requests on applications that have small or variable amounts of traffic.