[google-appengine] Shared memcache not working on Nodejs

2017-04-17 Thread Srikanth Kakani
Hi, I am trying out Shared memcache for my project (low volume right now). I am not able to connect to it with the following error: Error when trying to fetch from memcache Error: socket timed out waiting on response. at timeoutHandler (/app/node_modules/memjs/lib/memjs/server.js:206:18) at So

Re: [google-appengine] Shared memcache not working on Nodejs

2017-04-17 Thread 'Justin Beckwith' via Google App Engine
Greetings folks, Apologies for the confusion here. The memcache support for App Engine flexible is currently in alpha: https://cloud.google.com/appengine/docs/flexible/nodejs/upgrading#memcache_service You can fill out the form to get access, or take a look at the memcache support in redislabs: h

Re: [google-appengine] Shared memcache not working on Nodejs

2017-04-17 Thread Geoffrey Arnold
Hey Justin, thanks for the pointer! Very exciting. Is the memcache Alpha available for custom runtimes in the flexible environment? On Mon, Apr 17, 2017 at 12:30 PM, 'Justin Beckwith' via Google App Engine < google-appengine@googlegroups.com> wrote: > Greetings folks, > Apologies for the confusi

Re: [google-appengine] Shared memcache not working on Nodejs

2017-04-17 Thread 'Justin Beckwith' via Google App Engine
Yes, it should work great from custom runtimes. On Mon, Apr 17, 2017 at 1:07 PM, Geoffrey Arnold wrote: > Hey Justin, thanks for the pointer! Very exciting. > > Is the memcache Alpha available for custom runtimes in the flexible > environment? > > On Mon, Apr 17, 2017 at 12:30 PM, 'Justin Beckwi

Re: [google-appengine] Shared memcache not working on Nodejs

2017-04-17 Thread Geoffrey Arnold
Awesome, just filled out the form! Looking forward to it! On Mon, Apr 17, 2017 at 3:14 PM, 'Justin Beckwith' via Google App Engine < google-appengine@googlegroups.com> wrote: > Yes, it should work great from custom runtimes. > > On Mon, Apr 17, 2017 at 1:07 PM, Geoffrey Arnold < > geoffrey.arn...