On Mon, Sep 3, 2012 at 7:52 PM, Mos <[email protected]> wrote: > The last three days the GAE instance scheduler works accurate again. > There are just 1 or 2 loading-requests the day. Remember: The weeks before I > head hundreds of loading-request and many DeadlineExceededException.
Hi Mos, > > But no status-update from Google on > http://code.google.com/p/googleappengine/issues/detail?id=8004 ? I just updated the issue with more details. > > What has happened? > > - Just luck ? > - Did some GAE infrastructure / policy changed on 1th September ? > - Did somebody fix the weird instance scheduler? Perhaps after his or her > summer holiday ? > - Or did praying help ? > > Please Google, be transparent on this issue. I had a downtime of 5h 19m in > August (99,29%) in August. As we discussed before what you refer as downtime is actually a percentage of (loading) requests taking more than 5 seconds (and indenfied by *pingdom* as downtime). The App Engine SLA doesn't have the same definition of downtime https://developers.google.com/appengine/sla """ "Downtime" means more than a ten percent Error Rate for any Eligible Application. "Downtime Period" means, for an Application, a period of five consecutive minutes of Downtime. Intermittent Downtime for a period of less than five minutes will not be counted towards any Downtime Periods. "Error rate" for the Service is defined with the Covered Services. """ As of today, the App Engine SLA only covers the following components, https://developers.google.com/appengine/sla_error_rate. """ - Serving Infrastructure (HTTP Request sent to App Engine that results in an INTERNAL_SERVING_ERROR) - Datastore (Datastore api call returning one of the following errors: INTERNAL_ERROR, TIMEOUT, BIGTABLE_ERROR, COMMITTED_BUT_STILL_APPLYING, TRY_ALTERNATE_BACKEND ) """ And unfortunately loading request latency is not covered by the SLA yet. The serving infrastructure team is constantly working on improving the reliability of loading requests performance, but this is a long term effort and in the meantime we (and the App Engine community) can help you to optimize the performance on your application. > Other people had similar experiences. We need to know if reliability of GAE > is fixed durably! > > Thanks > Mos > > > > > On Fri, Aug 31, 2012 at 4:51 PM, Mos <[email protected]> wrote: >> >> Today again hundreds of useless instance restarts and many >> DeadlineExceededException. >> (Tried many configuration issues. Nothing helps. My last try : >> max-idle-instance to one) >> >> Any news on http://code.google.com/p/googleappengine/issues/detail?id=8004 >> ? >> >> As Kris wrote below the problem exists now for one month! >> >> GOOGLE, PLEASE FIX THE CRITICAL PRODUCTION PROBLEM .. we are loosing >> every day money and customer as long as GAE/Java works like junk !! >> >> I deeply regret to trust Google/GAE and build our application for this >> PaaS. >> >> Mos >> >> >> >> On Fri, Aug 31, 2012 at 3:48 AM, Kristopher Giesing >> <[email protected]> wrote: >>> >>> I posted a great deal of information in the thread here: >>> >>> >>> https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/rjZhjMEAXUI >>> >>> In that thread I posted logs that showed that the very first request >>> after setting min instances to 1 will spawn a new instance (in addition to >>> the instance that the min instances setting created). The app ID used in >>> that testing is "titan-game-qa" and the timestamps are in the logs I posted. >>> >>> At some point I will have enough bandwidth to set up a more specific >>> test, but I feel I've already posted plenty of information for GAE engineers >>> to digest. >>> >>> - Kris >>> >>> On Monday, August 27, 2012 2:17:47 AM UTC-7, Johan Euphrosine (Google) >>> wrote: >>>> >>>> On Mon, Aug 27, 2012 at 7:17 AM, Kristopher Giesing >>>> <[email protected]> wrote: >>>> >> Resident instances are used for processing incoming request if there >>>> >> is no dynamic instance >>>> > >>>> > >>>> > This is the behavior we all want, but experimentation seems to >>>> > indicate it >>>> > doesn't happen, at least for some apps. >>>> >>>> Hi Kristopher, >>>> >>>> Can you comment with the appid and timestamps of when this last >>>> happened? >>>> >>>> Thanks in advance. >>>> >>>> > >>>> > - Kris >>>> > >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> > Groups >>>> > "Google App Engine" group. >>>> > To view this discussion on the web visit >>>> > https://groups.google.com/d/msg/google-appengine/-/_wh1KzpESLEJ. >>>> > >>>> > 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. >>>> >>>> >>>> >>>> -- >>>> Johan Euphrosine (proppy) >>>> Developer Programs Engineer >>>> Google Developer Relations >> >> > > -- > 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. -- Johan Euphrosine (proppy) Developer Programs Engineer Google Developer Relations -- 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.
