Alexis, It looks that GEA has hidden balancing/lack of resources problems or deadlocks both results in RANDOM problems.
I think about moving to HRD but it looks that you suffer same on HRD the last days so it will not help till GEA will not generate RANDOM problems - I do some optimization it helps with time but not yet with availability. Day Total checks Outages Failed checks Avg. response time Uptime 2012.01.14 26 1 1 3.152 96.154 % 2012.01.15 47 1 1 4.937 97.872 % 2012.01.16 48 4 5 3.699 89.583 % 2012.01.17 48 3 5 2.507 89.583 % 2012.01.18 48 1 1 2.419 97.917 % 2012.01.19 47 2 2 3.143 95.745 % On 18 Sty, 11:02, Alexis <alexis.hanico...@gmail.com> wrote: > Cezary, I was in the same position in August, with our Python apps on > M/S. > The DEE errors began to appear, then were more and more frequent and > finally had a high impact on our app availability. > Our warmup requests, that only load code, were randomly taking from a > few secs to more than 30sec and so triggering the DEE. > > I could not figure out how it could be linked to the datastore, but > Google team only had one word to mouth: move to HRD. > No explanation at that time and made so sense for me but I decided to > trust them. > > We migrated to HRD writing our own mapreduce and then all went fine > (except for the costs that went higher but hey, was the price for a > more reliable > solution). > > But since something like mid-December, exactly the same symptoms > begin to appear again. Less frequent and not really impacting our > availability yet, but still there. > And no official acknowledgement of this issue so far... -- 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.
