DeadlineExceededError importing modules

[Chip]

We're suddenly seeing a spike of DeadlineExceededError errors that
look like the GAE is having trouble importing its built-in modules.
Its an HR application in Python. This application is pre-release and
getting very little traffic.

Here's a sample error, but it seems to happen with many different
modules:

<class 'google.appengine.runtime.DeadlineExceededError'>:
Traceback (most recent call last):
File "/base/data/home/apps/[appid]/1.355978131891365971/stream.py",
line 8, in <module>
import stdinclude
File "/base/data/home/apps/[appid]/1.355978131891365971/
stdinclude.py", line 17, in <module>
from google.appengine.ext.webapp import template
File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/webapp/template.py", line 68, in <module>
import django.template
File "/base/python_runtime/python_lib/versions/third_party/
django-1.2/django/template/__init__.py", line 60, in <module>
from django.utils.text import smart_split,
unescape_string_literal, get_text_list
File "/base/python_runtime/python_lib/versions/third_party/
django-1.2/django/utils/text.py", line 1, in <module>
import re

Note that this is the entire error, which indicates to me the problem
is with importing modules.

[Chip]

I'm wondering if one or more instances could be corrupt? When an end
user encounters a page with the DeadlineExceededError, they get a
server error:

"Error: Server Error

The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this
error message and the query that caused it."

We're seeing this same error sometimes when looking at the logs
through the dashboard. Could it be that one or more of the instances
that we get dynamically assigned are in a bad state? I assume our
dashboard uses the same instances as our application?

[Rajkumar Radhakrishnan]

Hi Chip,

Sorry to hear that you are facing errors for your app too.

This has been a recurring issue for my app recently..

http://groups.google.com/group/google-appengine/browse_thread/thread/47a765bf9740c951/6f766324e3a0d4d2

Even though my app is on MS, the actual datastore queries are pretty fast. It is the time to load the application and the time to write out django templates that is taking more time and incidentally they both involve reading/loading the application's uploaded files.

I had mentioned about this in a comment to my production issue on Dec 29th..

http://code.google.com/p/googleappengine/issues/detail?id=6629#c3 

But sadly there has been no word regarding this from Google staff. Mine is a paid-app used by many users for storing their data online. If you can afford to move away from Google App Engine, you should do so now.. before you regret for having bet on the wrong platform.

Regards,

Raj

--
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-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Chip]

The application is now unusable. More than 50% of the requests fail
with the DeadlineExceededError.

Other requests (with the same URL's) return very quickly. Again, the
only explanation I can think of for this is a problematic Instance (or
other shared resource). If the request goes the broken Instance (or
resource), the result is catastrophic. If it goes to another
Instance, it works fine. And the dashboard logs also fail frequently
with a 500 error.

Help!

[John B]

I'm having the exact same problem. It seems that it has been
intermittent for about 1-2 weeks, and judging from another thread on
here (http://groups.google.com/group/google-appengine/browse_thread/
thread/47a765bf9740c951/d0b91e8977e36c77?
hl=en&lnk=gst&q=DeadlineExceededError#d0b91e8977e36c77) there are a
few people experiencing this.

Google staff, what the hell is going on here?

[Chip]

I was mistaken.  This app is M/S (we have another app which is HR).
 So I guess the fix is to migrate it over to HR.

--Chip