Jeff, If what you said is true, then Google should be honest about it and say that all M/S app hosting clusters are deprecated, and they should clearly state that "Any latency related issues on M/S-based apps will not be investigated". I have not seen such unambiguous statements from anyone at Google. I do agree though that the strongest reason yet to move to HRD is to make Google pay closer attention to bug reports.
On Wed, May 23, 2012 at 1:37 AM, Jeff Schnitzer <[email protected]> wrote: > While I am sympathetic to your plight, I think there's a mistaken > assumption in this issue. > > A number of Google comments in public threads have led me to believe that > M/S apps run in entirely separate clusters (possibly in entirely separate > datacenters) from HRD apps. It's likely that all of the infrastructure - > memcache, task queue, urlfetch, etc - are separate. When Google says > "we're deprecating Master/Slave" they're really thinking "we're deprecating > the entire cluster", including all these other services. So when anything > at all goes wrong in the old cluster, the solution is the same - move to > HRD. > > There may very well be problems with memcache in the HRD cluster(s), but > it will be hard to get anyone to pay attention unless the issue is > demonstrated. This is a little like someone reporting a bug in a very old > version of a piece of software. Yes, that bug shouldn't be there, and > maybe it is still present in the new version, but the first step towards a > solution is still "upgrade". Nobody pays attention to bug reports in > obsolete software. > > So... upgrade to HRD. At the very least this will cause Google to pay > closer attention to your bug reports. It might even fix the issue. > > Jeff > > On Tue, May 22, 2012 at 9:55 PM, Rishi Arora <[email protected]>wrote: > >> If you believe this may be because of memcache API latency, please star >> this issue: >> http://code.google.com/p/googleappengine/issues/detail?id=7554 >> >> >> On Tue, May 22, 2012 at 11:44 PM, Daniel <[email protected]> wrote: >> >>> I'm seeing the same issue.. for the last 3 >>> days latency has skyrocketed and my costs have over doubled. Here's my >>> graph for the past 7 days >>> >>> >>> >>> <https://lh5.googleusercontent.com/-JCpRQX6MeFk/T7xrHDMMX8I/AAAAAAAAAzk/LcVjYw1awMo/s1600/skywords.jpg> >>> >>> >>> On Tuesday, May 22, 2012 2:04:53 PM UTC-7, Rishi Arora wrote: >>>> >>>> Here's what my milliseconds/request looks like, although the #instances >>>> follows a similar pattern, and translates directly into higher costs (5x >>>> normal usage today) >>>> >>>> On Tue, May 22, 2012 at 4:01 PM, Rishi Arora <[email protected] >>>> > wrote: >>>> >>>>> Perhaps similar to what I'm seeing. Although I was able to use the >>>>> appstats tool to determine that the deadlines were being missed >>>>> specifically because of memcache API calls. Perhaps you can determine >>>>> from >>>>> appstats if its the same for you? >>>>> >>>>> If so, please star this issue that I logged: >>>>> >>>>> code.google.com/p/**googleappengine/issues/detail?**id=7554<http://code.google.com/p/googleappengine/issues/detail?id=7554> >>>>> >>>>> >>>>> >>>>> On Tue, May 22, 2012 at 2:02 PM, Robert Morgan <[email protected] >>>>> > wrote: >>>>> >>>>>> Beginning about 18 hours ago, the milliseconds/Request on one of our >>>>>> apps began to ramp and is now over 100 seconds for a trivial response >>>>>> (which historically takes 2 seconds). Our other apps are fine, and the AE >>>>>> status page is clear. >>>>>> >>>>>> It's an app that we use for development, it's been around for ages >>>>>> and still runs the Master-Slave datastore. Python. The ramping just >>>>>> started >>>>>> -- we had not deployed a new server version in about a week, and our >>>>>> client >>>>>> usage remains low and patterns haven't changed. >>>>>> >>>>>> I've poked at it trying to see if I can determine some threshold, but >>>>>> even a very simple return now fails due to DeadlineExceeded. >>>>>> >>>>>> This really feels like it's a system issue -- any ideas on what I can >>>>>> do next? >>>>>> >>>>>> Thanks, >>>>>> :R >>>>>> >>>>>> -- >>>>>> 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/-/**rYY5Gw9UuE8J<https://groups.google.com/d/msg/google-appengine/-/rYY5Gw9UuE8J> >>>>>> . >>>>>> To post to this group, send email to google-appengine@googlegroups.** >>>>>> com <[email protected]>. >>>>>> To unsubscribe from this group, send email to >>>>>> google-appengine+unsubscribe@**googlegroups.com<google-appengine%[email protected]> >>>>>> . >>>>>> For more options, visit this group at http://groups.google.com/** >>>>>> group/google-appengine?hl=en<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 view this discussion on the web visit >>> https://groups.google.com/d/msg/google-appengine/-/eDY4e0D-tH4J. >>> >>> 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. >> > > -- > 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.
