See http://code.google.com/p/googleappengine/issues/detail?id=1298 .
On Oct 30, 5:24 am, Stephen <sdea...@gmail.com> wrote:
> On Oct 29, 11:20 pm, Tim Hoffman <zutes...@gmail.com> wrote:
>
> > Hi
>
> > I am not using DJango, and they where asking for automagic recycling.
>
> It's not django specific. Unusual latency anywhere in the system,
> including Google's api calls, might trigger a DeadlineExceededError.
> The various scenarios are too byzantine to expect people to get this
> 100% right. And the failure mode is pretty bad.
>
> > I would prefer to see the ability to explicit shut the instance (and
> > therefore let a new one respawn) if you detect the problem.
>
> But that's not a bad idea also.
>
> I haven't tested this, but you could try provoking the system into
> killing your instance. Something like:
>
> __too_much_memory = []
>
> def suicide():
> global __too_much_memory
> for n in xrange(1000 * 1000 * 1000 * 1000):
> __too_much_memory.append('If we blow our memory limit, maybe
> google will kill us...')
--~--~---------~--~----~------------~-------~--~----~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
