I still am still getting bursts of DeadLine exceeded errors during
imports every few days (in the morning US time)

T

On Sep 29, 5:46 am, Jason C <[email protected]> wrote:
> The last DeadlineExceededError for vendastaweb was at 09-28 07:44AM
> 56.147, so perhaps something has been adjusted.
>
> Officially not seeing DeadlineExceededErrors anymore at the moment!
> Good stuff!
>
> Dying to know more details.... ;)
>
> j
>
> On Sep 26, 12:19 pm, Jason C <[email protected]> wrote:
>
> > Hi Jeff,
>
> > We are still seeing the DeadlineExceededError in one of our apps
> > 'vendastaweb'. I can't find examples in our other apps at the moment.
>
> > An example stacktrace is as follows, but they are all different.
>
> > 09-26 06:48AM 39.093
> > <class 'google.appengine.runtime.DeadlineExceededError'>:
> > Traceback (most recent call last):
> >   File "/base/data/home/apps/vendastaweb/trunk-8081.335730273874884367/
> > main.py", line 111, in <module>
> >     main()
> >   File "/base/data/home/apps/vendastaweb/trunk-8081.335730273874884367/
> > main.py", line 77, in real_main
> >     util.run_wsgi_app(application)
> >   File "/base/python_lib/versions/1/google/appengine/ext/webapp/
> > util.py", line 76, in run_wsgi_app
> >     result = application(env, _start_response)
> >   File "/base/python_lib/versions/third_party/django-1.0/django/core/
> > handlers/wsgi.py", line 239, in __call__
> >     response = self.get_response(request)
> >   File "/base/python_lib/versions/third_party/django-1.0/django/core/
> > handlers/base.py", line 67, in get_response
> >     response = middleware_method(request)
> >   File "/base/python_lib/versions/third_party/django-1.0/django/
> > middleware/common.py", line 56, in process_request
> >     if (not _is_valid_path(request.path_info) and
> >   File "/base/python_lib/versions/third_party/django-1.0/django/
> > middleware/common.py", line 142, in _is_valid_path
> >     urlresolvers.resolve(path)
> >   File "/base/python_lib/versions/third_party/django-1.0/django/core/
> > urlresolvers.py", line 246, in resolve
> >     return get_resolver(urlconf).resolve(path)
> >   File "/base/python_lib/versions/third_party/django-1.0/django/core/
> > urlresolvers.py", line 181, in resolve
> >     sub_match = pattern.resolve(new_path)
> >   File "/base/python_lib/versions/third_party/django-1.0/django/core/
> > urlresolvers.py", line 181, in resolve
> >     sub_match = pattern.resolve(new_path)
> >   File "/base/python_lib/versions/third_party/django-1.0/django/core/
> > urlresolvers.py", line 124, in resolve
> >     return self.callback, args, kwargs
> >   File "/base/python_lib/versions/third_party/django-1.0/django/core/
> > urlresolvers.py", line 130, in _get_callback
> >     self._callback = get_callable(self._callback_str)
> >   File "/base/python_lib/versions/third_party/django-1.0/django/utils/
> > functional.py", line 130, in wrapper
> >     result = func(*args)
> >   File "/base/python_lib/versions/third_party/django-1.0/django/core/
> > urlresolvers.py", line 57, in get_callable
> >     lookup_view = getattr(__import__(mod_name, {}, {}, ['']),
> > func_name)
> >   File "/base/data/home/apps/vendastaweb/trunk-8081.335730273874884367/
> > vendastaweb/views/__init__.py", line 10, in <module>
> >     from vendastaweb.models.feed import Feed
> >   File "/base/data/home/apps/vendastaweb/trunk-8081.335730273874884367/
> > vendastaweb/models/feed.py", line 12, in <module>
> >     import feedparser
> >   File "/base/data/home/apps/vendastaweb/trunk-8081.335730273874884367/
> > lib/feedparser.py", line 113, in <module>
> >     import cjkcodecs.aliases
>
> > On Sep 25, 2:36 pm, "Jeff S (Google)" <[email protected]> wrote:
>
> > > Hi all,
>
> > > Thank you for all of the detailed reports. We've made some changes
> > > which should have improved the deadline exception situation,
> > > especially when related to a large number of imports when spinning up
> > > a new instance of an app. Since the fix has gone out we've been
> > > closely monitoring these apps but if you are still seeing issues
> > > please post here with your app ID, imports, and stack traces. Thanks
> > > again and apologies for the latency induced errors.
>
> > > Happy coding,
>
> > > Jeff
>
> > > On Sep 23, 2:10 pm, Jason C <[email protected]> wrote:
>
> > > > We are using Django 1.0.2 via zipimport and the most recent
> > > > appengine_django (r90), and are still seeing the
> > > > DeadlineExceededErrors.
>
> > > > Taro, please repost here again and update us in a day or two.
>
> > > > j
>
> > > > On Sep 23, 2:59 am, Taro Morimoto <[email protected]> wrote:
>
> > > > > Hi!
>
> > > > > I had the same problem with very high latencies and
> > > > > DeadlineExceededErrors. I don't know if you have the same problem as I
> > > > > did but I hope this helps for some of you.
>
> > > > > I'm using django 1.0.2 with zip import. So I just updated my google-
> > > > > app-engine-django helper library and the latencies are now gone. :)
>
> > > > > Best regards,
> > > > > Taro
>
> > > > > On Sep 19, 2:17 am, Michael <[email protected]> wrote:
>
> > > > > > I'm having the same problem (app: sovpad)
>
> > > > > > Except from my logs can be found 
> > > > > > here:http://groups.google.com/group/google-appengine-python/browse_thread/...
>
> > > > > > On Sep 19, 1:05 am, bvelasquez <[email protected]> wrote:
>
> > > > > > > I'm experiencing this also (app: jacob-6).  2 Sept. is when I 
> > > > > > > started
> > > > > > > noticing the issue.  Mostly in the morning (PST).  Later in the 
> > > > > > > day,
> > > > > > > the app is very fast, and responses come back after 200ms.  In the
> > > > > > > morning, these same requests can take up 20000ms.
>
> > > > > > > Barry
>
> > > > > > > On Sep 18, 9:28 am, johnP <[email protected]> wrote:
>
> > > > > > > > Dozens of people have been starring the following 
> > > > > > > > item:http://code.google.com/p/googleappengine/issues/detail?id=1695
>
> > > > > > > > Something happened after the 2 Sept deployment.
>
> > > > > > > > On Sep 18, 7:42 am, Mahmoud <[email protected]> wrote:
>
> > > > > > > > > Actually, our app (spont.appspot.com) has been seeing 
> > > > > > > > > elevated latency
> > > > > > > > > as well in the last two weeks. The code has not changed at 
> > > > > > > > > all in
> > > > > > > > > those two weeks.
>
> > > > > > > > > -M
>
> > > > > > > > > On Sep 18, 4:54 am, "Nick Johnson (Google)" 
> > > > > > > > > <[email protected]>
> > > > > > > > > wrote:
>
> > > > > > > > > > Hi Brandon,
> > > > > > > > > > What is your App ID?
>
> > > > > > > > > > On Fri, Sep 18, 2009 at 8:46 AM, Brandon Thomson 
> > > > > > > > > > <[email protected]> wrote:
>
> > > > > > > > > > > I get bursty periods of very high request latency, with 
> > > > > > > > > > > increasing
> > > > > > > > > > > frequency over the last few weeks, which last from 
> > > > > > > > > > > seconds to hours.
> > > > > > > > > > > Usually the elevated latencies are in the 3-6s range but 
> > > > > > > > > > > sometimes it
> > > > > > > > > > > goes up into the 20-30s range. For example, here are some 
> > > > > > > > > > > logs from a
> > > > > > > > > > > few minutes ago:
>
> > > > > > > > > > >      09-18 12:23AM 46.511 /checkStatus 500 2906ms 
> > > > > > > > > > > 105cpu_ms
> > > > > > > > > > > 8api_cpu_ms 0kb Pingdom.com_bot_version_1.4_(http://
> > > > > > > > > > >www.pingdom.com/),gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 46.511 /checkStatus 500 2906ms 
> > > > > > > > > > > 105cpu_ms
> > > > > > > > > > > 8api_cpu_ms 0kb Pingdom.com_bot_version_1.4_(http://
> > > > > > > > > > >www.pingdom.com/),gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 46.360 /stats 200 2771ms 105cpu_ms 
> > > > > > > > > > > 8api_cpu_ms 5kb
> > > > > > > > > > > w3m/0.5.2,gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 46.118 /admin/tick 200 2706ms 113cpu_ms
> > > > > > > > > > > 16api_cpu_ms 0kb Python-urllib/2.5,gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 43.878 /admin/tick 200 3825ms 113cpu_ms
> > > > > > > > > > > 16api_cpu_ms 0kb Python-urllib/2.5,gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 41.639 /admin/tick 200 4983ms 113cpu_ms
> > > > > > > > > > > 16api_cpu_ms 0kb Python-urllib/2.5,gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 41.603 /stats 200 4602ms 105cpu_ms 
> > > > > > > > > > > 8api_cpu_ms 5kb
> > > > > > > > > > > w3m/0.5.2,gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 41.603 /stats 200 4602ms 105cpu_ms 
> > > > > > > > > > > 8api_cpu_ms 5kb
> > > > > > > > > > > w3m/0.5.2,gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 39.401 /admin/tick 200 4826ms 113cpu_ms
> > > > > > > > > > > 16api_cpu_ms 0kb Python-urllib/2.5,gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 39.401 /admin/tick 200 4826ms 113cpu_ms
> > > > > > > > > > > 16api_cpu_ms 0kb Python-urllib/2.5,gzip(gfe),gzip(gfe)
> > > > > > > > > > >      09-18 12:23AM 37.158 /admin/tick 200 4800ms 113cpu_ms
> > > > > > > > > > > 16api_cpu_ms 0kb Python-urllib/2.5,gzip(gfe),gzip(gfe)
>
> > > > > > > > > > > Pingdom is pinging from all over the globe and sees the 
> > > > > > > > > > > problem so it
> > > > > > > > > > > is definitely on the App Engine side.
>
> > > > > > > > > > Can you elaborate on this?
>
> > > > > > > > > > > Drilling down into my logs: Even when the requests are 
> > > > > > > > > > > taking 6s+ to
> > > > > > > > > > > return, from my first logging statement at the very top 
> > > > > > > > > > > of my python
> > > > > > > > > > > file to the last logging statement at the end of my 
> > > > > > > > > > > request handler is
> > > > > > > > > > > only 500ms of real time. So, I don't know where exactly 
> > > > > > > > > > > the issue is,
> > > > > > > > > > > but it doesn't seem to be inside my code.
>
> > > > > > > > > > What imports, other than 'logging' are you doing before 
> > > > > > > > > > your first logging
> > > > > > > > > > statement?
>
> > > > > > > > > > > These requests all have < 200ms of latency most of the 
> > > > > > > > > > > time (although
> > > > > > > > > > > the bad behavior has gotten increasingly frequent lately).
>
> > > > > > > > > > > I thought this might be related to the problems the 
> > > > > > > > > > > Django folks are
> > > > > > > > > > > having with DeadlineExceeded errors... See
> > > > > > > > > > >http://code.google.com/p/googleappengine/issues/detail?id=1695and
> > > > > > > > > > > many other discussion threads linked therein.
>
> > > > > > > > > > --
> > > > > > > > > > Nick Johnson, Developer Programs Engineer, App Engine
> > > > > > > > > > Google Ireland Ltd. ::
>
> ...
>
> read more »
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to