I realize this is likely a GCS server issue and I don't mean to distact from that but I'd also like to point out that the SDK's google-api-python-client (which I assume GCS relies upon under the hood) is v1.0beta6 from Oct 28, 2011, where the latest release seems to be v1.2 from Aug 7, 2013. I assume the runtime versions on the live servers are up to date :) PKG-INFO snippets below:
--- Latest PKG-INFO snippet --- Metadata-Version: 1.1 Name: google-api-python-client Version: 1.2 Summary: Google API Client Library for Python Classifier: Development Status :: 5 - Production/Stable --- App Engine SDK 1.8.5 PKG-INFO snippet --- Metadata-Version: 1.0 Name: google-api-python-client Version: 1.0beta6 Summary: Google API Client Library for Python Classifier: Development Status :: 4 - Beta On Thursday, September 19, 2013 2:03:44 PM UTC-4, Vinny P wrote: > > On Thu, Sep 19, 2013 at 7:46 AM, Ben Smithers > <smithe...@googlemail.com<javascript:> > > wrote: > >> It looks like Vinny was correct - writes of a smaller size do not seem to >> cause a problem. Specifically, writes from backend instances to datastore, >> blobstore and cloud storage of 32KBs all display the hanging behaviour >> > > > Your experiences parallel mine - backend instances seem to have more > difficulty communicating with other Google services compared to frontend > instances. I often speculate that there is an additional communications > layer within the backends system, or different architectural decisions. > > > On Thu, Sep 19, 2013 at 11:53 AM, Ben Smithers > <smithe...@googlemail.com<javascript:> > > wrote: > >> In light of Doug's comments, I have also confirmed the same behaviour >> (success on writing 30KB; some hangs on writing >=32KBs) occurs with the >> latest release (r105) of the client library from SVN. I was expecting this, >> as it doesn't look like the GCS library is the problem. >> >> > > +1. I see similar behavior when communicating directly to GCS via the JSON > API. > > > On Thu, Sep 19, 2013 at 11:50 AM, Ye Yuan <y...@google.com <javascript:>> > wrote: >> >> Yeah from the evidences so far I am also hoping the hangs aren't >> originated from the GCS lib. >> >> > > Ye, I want to emphasize something since you're reading this thread. I > believe there are two different issues here: One, backend instance urlfetch > to anything (not just GCS) seems to be less stable than frontend instance > urlfetch (perhaps there's something chunking requests from the backend?). > Second, GCS itself (not the library, but GCS servers) seems to have > difficulty with differing chunk sizes. You wrote that GCS has a minimum > chunk size of 256KB, but I've flushed chunks much smaller than that > reliably and without difficulty. > > So the bottom line here is when you're testing, test from App Engine > frontend and backend instances, Compute Engine machines, and from an > external-to-Google-networks machine. I'd focus less on the client library. > > > ----------------- > -Vinny P > Technology & Media Advisor > Chicago, IL > > App Engine Code Samples: http://www.learntogoogleit.com > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
