我创建了一个GAE应用程序.这工作到今天早上都很好……

仍然没有那么多请求进入我的应用程序,但GAE一直重新生成我的实例…

现在当有人来到我的网站时,首先我会向服务器发出大约10个请求以获取一些数据,然后才能顺利完成.从今天起,这10个请求会导致很多请求/ _ah / warmup,如下所示,您可以在1秒内完成.结果我达到了“前端实例时间”的极限而没有真正发生的事情.

所以我想知道并希望有人可以告诉我是什么导致了这种情况发生,或者我如何解决这个问题,

谢谢,

2014-05-22 11:21:13.513 /_ah/warmup 200 7688ms 0kb module=default version=1
I 2014-05-22 11:21:13.512 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ

2014-05-22 11:21:13.093 /_ah/warmup 200 6838ms 0kb module=default version=1
I 2014-05-22 11:21:13.093 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ

2014-05-22 11:21:11.671 /_ah/warmup 500 5794ms 0kb module=default version=1
I 2014-05-22 11:21:11.670 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ
E 2014-05-22 11:21:11.670 Process terminated due to exceeding quotas.

2014-05-22 11:21:11.478 /_ah/warmup 500 5655ms 0kb module=default version=1
I 2014-05-22 11:21:11.475 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ
E 2014-05-22 11:21:11.475 Process terminated due to exceeding quotas.

2014-05-22 11:21:11.319 /_ah/warmup 200 5492ms 0kb module=default version=1
I 2014-05-22 11:21:11.319 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ

2014-05-22 11:21:10.403 /_ah/warmup 500 4587ms 0kb module=default version=1
I 2014-05-22 11:21:10.388 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ
E 2014-05-22 11:21:10.388 Process terminated due to exceeding quotas.

2014-05-22 11:21:10.310 /_ah/warmup 200 4494ms 0kb module=default version=1
I 2014-05-22 11:21:10.310 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ

2014-05-22 11:20:33.941 /_ah/warmup 200 7059ms 0kb module=default version=1
I 2014-05-22 11:20:33.941 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ

2014-05-22 11:20:33.698 /_ah/warmup 200 7106ms 0kb module=default version=1
I 2014-05-22 11:20:33.697 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ

2014-05-22 11:20:33.161 /_ah/warmup 200 6731ms 0kb module=default version=1
I 2014-05-22 11:20:33.161 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ

2014-05-22 11:20:12.854 /_ah/warmup 503 18ms 0kb module=default version=1

2014-05-22 10:19:51.619 /_ah/warmup 500 4085ms 0kb module=default version=1
I 2014-05-22 10:19:51.618 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ
E 2014-05-22 10:19:51.618 Process terminated due to exceeding quotas.

最佳答案 我有同样的错误.我在跟踪标签中看到了错误,但没有在日志中看到错误.我问了很多地方,最后得到了这个答案：

it appears that the 500 warmup errors you are seeing do not indicate
an error in your application. They are rather used internally as
signal messages in our architecture. That explains why you are not
seeing them in the Logs but only in Trace and why they are marked as
healthy messages. As Cloud Trace is still in beta it is understandable
to see minor inconsistencies.