Awesome!!!
(via cellphone, random spelling ahead)
On Dec 31, 2015 5:30 AM, "John Lowry" wrote:
> Hi ,
>
> Our engineers have isolated an issue in our infrastructure that caused
> occasional slow Datastore RPCs for a small number of apps from 2015-12-27
> 19:10 through
Hi ,
Our engineers have isolated an issue in our infrastructure that caused
occasional slow Datastore RPCs for a small number of apps from 2015-12-27
19:10 through 2015-12-29 15:20.
If your issue is still ongoing, then please file a support case and we can
investigate further.
John Lowry
yes, we're seeing many timeouts of the same sort... across multiple
libraries. we've submitted a ticket
Timeout: The datastore operation timed out, or the data was temporarily
unavailable
DeadlineExceededError: The API call datastore_v3.Delete() took too long to
respond and was cancelled
weird - the datastore timeouts went away, but then came back this morning.
nobody else is seeing this?
adam
On Tuesday, December 29, 2015 at 10:37:42 AM UTC+11, Adam Sah wrote:
>
> anyone else seeing increased datastore timeouts? I've confirmed that
> traffic levels are normal i.e. not
I can confirm that our Java app is also having lots of datastore timeouts.
We still use MS... Is this another hint to go ahead and jump into HRD?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
Folks @appengine, atleast reply this post. Even i provide better
customer service then this for my company that earns a fraction of
what Google does.
On Jul 19, 1:14 pm, Ronoaldo José de Lana Pereira
rpere...@beneficiofacil.com.br wrote:
I can confirm that our Java app is also having lots of
Might try a production issue:
http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
On Tue, Jul 19, 2011 at 13:19, vivpuri v...@vivekpuri.com wrote:
Folks @appengine, atleast reply this post. Even i provide better
customer service then this for my company that
My app is getting hundreds of datastore timeouts. Status dashboard is
also showing elevated latency for datastore. Can someone from
AppEngine team please respond and provide an ETA on this issue
On Jul 15, 2:19 pm, vivpuri v...@vivekpuri.com wrote:
My app is throwing tons of datastore
Same here. Since about 13-14 hours. Even pages that are not much dependent
on DB are timing out.
On Tue, Jul 19, 2011 at 7:32 AM, vivpuri v...@vivekpuri.com wrote:
My app is getting hundreds of datastore timeouts. Status dashboard is
also showing elevated latency for datastore. Can someone
If you are referring to
http://appengine-cookbook.appspot.com/recipe/autoretry-datastore-timeouts/,
yes it really works. A second try at reading from the datastore *is*
nearly always successful. (I think once it took a 3rd try.) I would
recommend this code for almost any app.
On Jan 23, 6:25
I was seeing this problem again few minutes ago.
It's certainly only on writes. (I switched app version to save logs.
If you want, you can look at logs of beta19, app id: sovpad).
It lasted around 5 minutes (6:32 - 6:37)
On Oct 22, 1:47 am, Michael m...@mzlab.net wrote:
Timeouts were on writes
I'm experiencing a lot of 500ers when accessing App Engine apps or
dashboard.
Something weird in going on there...
On 22 Okt., 15:46, Michael m...@mzlab.net wrote:
I was seeing this problem again few minutes ago.
It's certainly only on writes. (I switched app version to save logs.
If you
seeing a lot of datastore read latency on multiple apps
On Oct 22, 10:04 am, dflorey daniel.flo...@gmail.com wrote:
I'm experiencing a lot of 500ers when accessing App Engine apps or
dashboard.
Something weird in going on there...
On 22 Okt., 15:46, Michael m...@mzlab.net wrote:
I was
We are currently investigating an issue with high latency and error
rate in the datastore.
--Matthew
On Oct 22, 7:04 am, dflorey daniel.flo...@gmail.com wrote:
I'm experiencing a lot of 500ers when accessing App Engine apps or
dashboard.
Something weird in going on there...
On 22 Okt.,
Hi Michael,
One possible cause could be that a Bigtable tablet which is used by your app
was in the process of being split, which can cause a short burst of timeouts
but ensure better performance going forward. Were these timeouts on just
writes or also reads?
Thank you,
Jeff
On Tue, Oct 20,
Timeouts were on writes (as far as i could tell looking at logs), the
problem
lasted for several minutes and i had time to post :)
On Oct 21, 11:37 pm, Jeff S (Google) j...@google.com wrote:
Hi Michael,
One possible cause could be that a Bigtable tablet which is used by your app
was in the
Hi Kenneth,
Occasional datastore timeouts are expected regardless of your usage
patterns. Under normal operation, they will occur very rarely, but
they will occur. You need to modify your code to handle this
eventuality.
-Nick Johnson
On Thu, May 14, 2009 at 11:03 AM, Kenneth
On Mar 31, 1:13 pm, WallyDD shaneb...@gmail.com wrote:
I seem to be getting a few datastore timeouts.
If I look at percentages it isn't really that much but it does clog up
the log. The timeouts tend to correspond with the spikes in
App Engine has always thrown timeouts, and they've always had
occasional timeout clusters like you describe. As far as I know, you
just have to handle them as best you can. Our app has a lot of logic
for tracking and resending AJAX and AMF requests to deal with this,
but because of the timeout
can you post the query ?
Sebastian E. Ovide
On Fri, Mar 6, 2009 at 9:07 PM, Brandon Thomson gra...@gmail.com wrote:
For me even fetching 1-2 entities can be too many and cause a Timeout.
It seems to depend on the complexity of the query.
I recommend you don't
For me even fetching 1-2 entities can be too many and cause a Timeout.
It seems to depend on the complexity of the query.
I recommend you don't do any queries until the issues are resolved:
just fetch entities by key. That still works just fine.
On Mar 6, 1:32 am, gobagoo atist...@gmail.com
On Feb 28, 5:49 pm, Alex Popescu the.mindstorm.mailingl...@gmail.com
wrote:
Today starting around 07.42am the datastore has started to through
Timeout exceptions. I haven't read anywhere about an announced
maintenance window, so I do consider this a critical issue.
Forgot to mention that I
I'm seeing this problem as well - seems to timeout well before the
allowed 30 seconds...
/Morten
On Feb 28, 4:53 pm, Alex Popescu the.mindstorm.mailingl...@gmail.com
wrote:
On Feb 28, 5:49 pm, Alex Popescu the.mindstorm.mailingl...@gmail.com
wrote:
Today starting around 07.42am the
http://code.google.com/status/appengine/
On 28/02/2009, morten mor...@fusemail.com wrote:
I'm seeing this problem as well - seems to timeout well before the
allowed 30 seconds...
/Morten
On Feb 28, 4:53 pm, Alex Popescu the.mindstorm.mailingl...@gmail.com
wrote:
On Feb 28, 5:49
On Feb 28, 6:39 pm, Barry Hunter barrybhun...@googlemail.com wrote:
http://code.google.com/status/appengine/
The report seems wrong, as the traceroutes are showing Timeouts from
the datastore and not from memcache.
[code]
File /base/python_lib/versions/1/google/appengine/ext/db/
Be aware that there are times that memcache is disabled. At certain
maintenance activities memcache.get() always returns None and
memcache.set() has no effect.
And memcache will be cleared when maintenance is over and normal
behavior has returned.
Your application must be able to deal with this
2009/1/10 djidjadji djidja...@gmail.com:
Be aware that there are times that memcache is disabled. At certain
maintenance activities memcache.get() always returns None and
memcache.set() has no effect.
And memcache will be cleared when maintenance is over and normal
behavior has returned.
It does seem like the number of timeouts has increased in recent
weeks. I just checked my logs, and during the minute of 11:33am this
morning I had 43 timeout data store errors:
Traceback (most recent call last):
File /base/python_lib/versions/1/google/appengine/ext/webapp/
__init__.py, line
As an example, of how frequently datastore write timeouts are
happening on app engine, here are the last 20 entries in my production
error log, showing 20 timeouts in 15 minutes!
I'm hoping the Google team will break their silence about this and at
least acknowledge the problem.
Developers:
Hi Alex, sorry for the frustrations this is causing. The first thing I
would check for here is to verify that these writes are not failing
due to entity group contention. (documentation on entity groups:
30 matches
Mail list logo