Sorry, I forgot to add the obvious detail: This bug is triggered if the result of your datastore call is >1MB.
Cheers, Brian On Wed, Nov 9, 2011 at 1:22 PM, Brian Quinlan <[email protected]> wrote: > Hi Kaan, > > This is a bug in the Python 2.7 runtime that will be fixed with the > 1.6.1 release. > > Cheers, > Brian > > > On Wed, Nov 9, 2011 at 12:19 PM, Kaan Soral <[email protected]> wrote: >> I started getting a lot of >> (<class >> 'google.appengine.runtime.apiproxy_errors.ResponseTooLargeError'>, >> ResponseTooLargeError('The response from API call >> datastore_v3.RunQuery() was too large.',), <traceback object at >> 0x2e613c8>) >> errors from my crons >> >> These errors started after I switched to 2.7 and concurrency >> >> I am guessing now requests are not allowed a lot of memory, and these >> datastore calls are failing. >> >> I currently reduced the amount of entities from 40 to 20, an entity is >> maximum 1mb's and should be 100kb's on average. >> >> How should I fix this problem? >> >> -- >> 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. >> >> > -- 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.
