I'm seeing the same thing with the test app I created. Even though I had max instances set to 1 the scheduler still started up a second instance. During this time I had several request that resulted in 500 server errors. Once the second instance was started latency increased - as if the scheduler couldn't decide which instance to route the request to. After a few seconds it subsisted. I believe that this transition period maybe responsible for error rates. The bad thing about it is:
1) The errors didn't appear in the logs. So it is quite likely that this is a common problem, but few developers are aware of it. 2) There's nothing that can be done to fix it. In fairness I was testing under the free quota, so maybe the scheduler behaves better on payed apps. On Jul 9, 2012, at 10:05 PM, Richard wrote: > Ok, so I sat with Jeff in a G+ hangout for a while tonight, and we could not > figure it out - other than my app is confusing the crap out of the scheduler > which is then not sending requests to instances. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
