Clever Geek Handbook

Engine does not work in some applications

Some requests fail quietly in my python application, intermittently and unpredictably. The hallmarks of failure are:

  • The request returns 200, so the client doesn't know if there is a problem.
  • The request is NOT running on the server.
  • There are no records in the request.

Below is an example from my logs with a bunch of requests, each of which should write an object to the datastore. You can see the bottom, successful request, a blue "i" is present, indicating that level logs have been written info

. When I browse the datastore, an object has been successfully written for this request.

However, for the failed request, you can see that there is only a white square and no registration statements exist at all. Although the server returned 200, no objects were written to the data store for this request.

Log Viewer

Has anyone come across something like this before in App Engine? Any ideas on how to debug it? I've seen this myself in several different applications, but I've never been able to figure it out.

EDIT

To clarify, the main problem here is that the code is not being executed, as measured by the inability to write the object. Fake 200 and lack of registration are associated symptoms.

+3


source to share


1 answer


From a comment originally, but apparently this is the way to resolve this issue:

Considering there are no log statements on the line and you find yourself unpacking the arguments and logging them as soon as you step into the handler, it starts to look like an infrastructure / platform issue.



In such a case, your best bet is to open the Public Release Tracking issue , and Type-Production as a tag including your app id and timeframe as well as as much information as possible about your app and request handler, and platform support will help resolve the issue in sorting progress.

However, it's worth considering a handler to make sure you can't exit the handler and send 200 without registering or see an exception. It all depends on what the code is capable of handling, what stack it uses, etc.

+2


source






More articles:


All Articles