Mr. Wirtz, Thank you for your recommendation!
Unfortunately I would really not want this conversation to move to the 'why I get so many errors' realm, and as you can clearly see the examples I have given above are system wide daily errors rather then application specific errors. My original post specified 3 major system wide disruptions, but the rest of my post talked mainly of GAE team's handling of these disruptions. I perfectly know that there are errors caused by my company's system, and by our configuration - I am sure there are still many things we can do to make them better (Thank god we are far from 10% error rate on our account). I have no doubt that 99% of the time errors are caused by users' bugs rather then GAE's production issues. I would really want this conversation to move something in Google to make their handling of the system wide errors as transparent and honest as possible, to help us communicate as much information to our clients as we can. (Mr. D'alesandre, are you reading this? Am I achieving my goal somehow? :) ) I hope you understand why I am 'avoiding' your question, as I simply think it can take us out of the path of to the discussion I am trying to advance (Yes, I am limiting my max number of instances, and yes I know it can cause errors but I almost always have at least 2 idle instances, and my errors are at times where traffic is not at its maximum). - Yoav. On Nov 20, 2:58 am, "Brandon Wirtz" <[email protected]> wrote: > You avoided my question. Have you limited max idle instances. > > Failure before reaching the app can be that you have no available instances > to handle the request which was why I was asking if you had set max idle > instances. If those are set wrong you will get 500 errors up the wazoo and > never see a single error in your log. I have helped several people who > thought they were saving money by setting those to very low numbers only to > find out they were losing 10% of their traffic to errors. > > > > > > > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of trilok > Sent: Saturday, November 19, 2011 4:20 PM > To: Google App Engine > Subject: [google-appengine] Re: Google App Engine's Team Dishonesty > > OK, ok, ok, so we don't talk in theory (and to answer one question - the > errors are of requests that don't reach our app. They fail > before): -- 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.
