I am only guessing but I imagine that 'cluster' is some form of load balancing segment that Google uses to service and route requests to the virtual servers and this error/warning is indicative of when that queue is very busy. And regardless of if it is an error or a mere warning it still resulted in a 500, extremely high resource usage and a negative experience for the end user.
On Mon, Oct 11, 2010 at 12:56 PM, Jamie H <ja...@mhztech.com> wrote: > What do you mean by "cold instance startup that timed out" ? > > Sometimes I will get the error: > Request was aborted after waiting too long to attempt to service your > request. This may happen sporadically when the App Engine serving > cluster is under unexpectedly high or uneven load. If you see this > message frequently, please contact the App Engine team. > > I see this error occasionally when my site has NO load, so I assume > this is a cold instance startup that timed out? > > I've been trying to find out about this issue for a while with little > response. It is fairly troubling to see this error randomly in > several apps of mine. I never noticed it until I realized it is a > "warning" not an "error" so you must set your log severity > appropriately to find these. People have told me this error occurs > when all your apps instances are busy and requests wait too long in > queue for an instance. However, I see it when my site has NO load so > I don't quite believe this is always the case... > > On Oct 11, 11:30 am, Eli Jones <eli.jo...@gmail.com> wrote: > > Seems like if you want direct one on one comunication and service > > guarantees, you gotta try to get into the Appengine for Business preview: > > > > http://code.google.com/appengine/business/ > > > > <http://code.google.com/appengine/business/>But then.. you have to pay. > > > > Also, from seeing your logs below.. it really appears that the 8:07:46 > log > > was for a cold instance startup that timed out, the 8:07:59 log is for a > > cold start that succeeded, and the 8:08:05 log is for a hot instance. > > > > Are you sure that log number 2 (for 8:07:59) didn't have this additional > > info when you expand it?: > > > > "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 > > request may thus take longer and use more CPU than a typical request for > > your application." > > > > On Mon, Oct 11, 2010 at 12:19 PM, Jeff Schwartz <jefftschwa...@gmail.com > >wrote: > > > > > Here is an example of my logs: > > > 1) 10-11 08:08AM 05.539 /account.groovy 200 218ms 265cpu_ms > 13api_cpu_ms > > > 2kb Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.10) > > > Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0C),gzip(gfe) > 2) > > > 10-11 08:07AM 59.775 /account.groovy 200 2401ms 1976cpu_ms 13api_cpu_ms > > > 2kb Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.10) > > > Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0C),gzip(gfe) > 3) > > > 10-11 08:07AM 46.856 /account.groovy 500 10015ms 0cpu_ms 0kb > Mozilla/5.0 > > > (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.10) Gecko/20100914 > > > Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0C),gzip(gfe) All of the > above > > > are for the exact same code operating on the exact same data. > > > > > Excluding #3 above, the server was already live and ready to receive > > > requests. Notice the variance in response time for #1 & #2. That is > alarming > > > don't you think? > > > > > This is not indicative of a stable environment where one should be > billed > > > for using it. Once issues like these are resolved then billing would be > > > entirely acceptable. > > > > > Again, I don't believe I am being overly critical but I have yet to > receive > > > a response from anyone at Google regarding my plea for assistance. If > they > > > would prefer to contact me off-line via email then that would be wholly > > > agreeable on my part. > > > > > Jeff > > > > > -- > > > 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<google-appengine%2bunsubscr...@googlegroups.com> > <google-appengine%2bunsubscr...@googlegroups.com<google-appengine%252bunsubscr...@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-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Jeff -- 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-appeng...@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.
