Is app engine python 3 slightly unstable?

[maclek]

We went live with our python 3 migration this week and it has generally gone well but we are finding there is some instability / random errors that we didn't experience with python 2.

Specifically we are seeing the following:

• urlfetch calls are failing one or twice an hour, both to firebase and external servers.
• Users uploading to the blobstore with urls from create_upload_url are reporting errors even with very small files.
• Task are failing randomly with 302 errors that we are so far unable to diagnose.

It's not that busy a site, peaking at around 600 qps each day. It might be we're just finding our feet.

[robertcarlos]

Hi @maclek,

Welcome to Google Cloud Community!

Random errors or instability may be encountered after migration from Python 2 to 3 due to the following key differences:

• Compatibility issues between Python 2 and Python 3
• App Engine bundled services in the Python 3 runtime
• Configuration files differences
• A web framework is required to route requests for dynamic content
• Apps with only static content
• Testing differences
• Deployment differences

There are also some backward incompatible changes that were introduced to the latter like handling data, text and strings. There are also some libraries that were changed to be more compatible with Python 3.

You may check this documentation for your reference regarding migration information. You could also file a bug so that our engineers could take a look at this. We don't have a specific ETA but you can keep track of its progress once the ticket has been created.

Hope this helps.

[maclek]

I've found this issue https://github.com/GoogleCloudPlatform/appengine-python-standard/issues/105 which describes the root cause what we're facing.

@robertcarlos appreciate the effort but we're well beyond all that