Hi Ben,
On Jun 1, 9:35 pm, Ben Nevile wrote:
> About 90 minutes ago one of my applications began failing on somewhere
> close to 100% of its datastore API calls. The app is nowhere close to
> exceeding any quotas, and I haven't made any changes in the code in
> the last ... I don't know, at lea
Hi everyone,
This should be fixed now (similar to what's covered on
http://groups.google.com/group/google-appengine/browse_thread/thread/aa9de454f7cf0a1c#).
Sorry again for the trouble.
-Brett
Google App Engine Team
--~--~-~--~~~---~--~~
You received this me
Hey everyone,
We've isolated the cause of this issue and it should be fixed now.
Please let us know if you have any further problems! Sorry again for
the trouble.
-Brett,
Google App Engine Team
--~--~-~--~~~---~--~~
You received this message because yo
hurting our users'
> experience with our growing service. Any help would be much
> appreciated.
>
> Thanks
> Gee
>
> On Nov 13, 10:30 am, "Brett (Google)" <[EMAIL PROTECTED]>
> wrote:
>
> > Memcache calls should now be failing fast. That should
12 am, "Brett (Google)" <[EMAIL PROTECTED]>
wrote:
> Hi Gayle,
>
> Yes, the *request* times out during the API call. It's not the API
> call itself that's timing out. But there is no effective difference to
> your application if you're caught in this sit
Hi Gayle,
Yes, the *request* times out during the API call. It's not the API
call itself that's timing out. But there is no effective difference to
your application if you're caught in this situation (as you pointed
out). I'd assume the first few calls you make to memcache during a
request actual
