On Thu, Nov 13, 2014 at 8:06 AM, M.ES <http://m.es/> < [email protected]> wrote:
> I keep getting error code 202 for a period of time and then suddenly the > application start to work fine again. Furthermore, I noticed that instances > are killed after 1 minute;I do not know why! > > The above behavior happens once a week and I can't stop it! Last week the > application returned error 500 for an hour and then became stable again. > However, yesterday the application was down for 15 hours and I didn't know > what to do and suddenly it started to work again. > Google has never fully explained what error code 202 actually means. I suspect it's somewhat of a "catchall"/generic error code, similar to the 500 "Internal Server Error" error code for HTTP. But in past discussions, error code 202 generally seems to be related to resource exhaustion - capping out on memory, processing power, throughput throttles, etc. When your application goes down, is there a common thread involved? For instance, do you see urlfetch/memcache/datastore/whatever operations increasing in execution time immediately before the 202 error code pops? During the time when your application is down, do all requests cause a 202 error code? If you attempt to redeploy your application/disable and reenable your application during this downtime, does that fix the issue temporarily? If you change your instance classes to the next available level, does that reduce or remove the downtime you experience? ----------------- -Vinny P Technology & Media Consultant Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
