[google-appengine] Re: datastore timeout question
I lowered rpc deadline to 3 seconds... but transaction still fails after 30 seconds. It seems that taskqueue.Task().add(..., transactional=True) causes this. I also noticed that my errors are exactly during Task latency pikes http://code.google.com/status/appengine/detail/taskqueue/2011/02/23#ae-trust-detail-taskqueue-add-latency Can I lower deadline for task.add() function to prove this theory? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: datastore timeout question
https://lh6.googleusercontent.com/_nXv-kmjg1BQ/TWZXH_TkpXI/QoI/jAUULxOgkK4/chart.png another task queue peak... and db transaction errors again. Strange:) -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: datastore timeout question
I'm not aware of an 'easy' way to set an RPC deadline for a task insert. I think you could probably setup an RPC and make the add call yourself though. http://code.google.com/p/googleappengine/source/browse/trunk/python/google/appengine/api/taskqueue/taskqueue.py#752 I occasionally see issues inserting tasks, but 99% of the time it is a TransientError and will succeed on retry. You might try catching the error on task insert once and retrying it. Robert On Thu, Feb 24, 2011 at 04:58, Dmitry dmitry.lukas...@gmail.com wrote: I lowered rpc deadline to 3 seconds... but transaction still fails after 30 seconds. It seems that taskqueue.Task().add(..., transactional=True) causes this. I also noticed that my errors are exactly during Task latency pikes http://code.google.com/status/appengine/detail/taskqueue/2011/02/23#ae-trust-detail-taskqueue-add-latency Can I lower deadline for task.add() function to prove this theory? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: datastore timeout question
Dmity indicated a master/slave on-line handler failure caused by: --get by key, --put with updated value, --run new task to update stats within transaction (launching the TQ call, not finishing it I'll assume) My question on the failures on this lightweight process is whether the small failure rate could be due to an occasional spin-up of a new instance to handle that process?? Does your handler have a large amount of imports which might put even the lightest weight process at risk of a Deadline Exceeded error?? A failure rate like this for MS is apparently going to be part of the package, and that's fine by me. But, if such problems persist with HR and our only alternative is client-side handling (which Dmitry suggests may not be foolproof), then that is another issue. If MS is 1/3000 random failures, then hopefully HR can add a zero to the denominator (two would be better, but one is livable). thanks, stevep On Feb 21, 1:31 pm, Dmitry dmitry.lukas...@gmail.com wrote: Hi All! I'm trying to figure out the reason of my datastore timeouts. I use master/slave datastore. As I can see possible reasons are: - contention issues - A very small number of datastore operations – generally less than 1 in 3000 – will result in a timeout in normal operation (as per documentation) In my case it is acceptable error rate for background task operations (which retry automatically). For example (today stats) 127.58K tasks caused 192 errors. It is possible some contention errors here. But for user operations sometimes I have very high error rate (89 requests failed from 1.7K with datastore timeout). - I'm pretty sure I'm not trying to update the same entity group in the same minute (not even second) - transaction is small: get by key, put with updated value, run new task to update stats within transaction - I cannot retry operation within 30 seconds user request... I've added retry code - but It fails earlier - I cannot find any error patterns My questions are: 1. If this is a task queue issue - will transaction fail with datastore timeout? 2. Has High Replication datastore any difference in normal error rate (1 of 3000 for master/slave)? Just for the test I've created 2 applications (master/slave and HR) and ran my code (~40K task requests and random user actions). But results are not so obvious - master/slave failed 1 time with datastore error - no errors with HR May be due to small amount of data (~200MB in my test, possible only 1 tablet used). In real system I have around 190GB now. The error distribution (today 21/02): https://lh3.googleusercontent.com/_nXv-kmjg1BQ/TWLXXDQAwrI/Qn... The big issue that these errors are visible to the customers. Any suggestions? Thanks! -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: datastore timeout question
- no. there are no new instances spin-up that time - there are only from google.appengine.ext import db, webapp, from google.appengine.ext.webapp.util import run_wsgi_app and couple of my classes imports. I don't think this is an issue. normally this operation takes around 229ms 385cpu_ms 362api_cpu_ms -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Datastore timeout error trapping - help needed please.
Thanks for the reply, that's excellent, that's great I can remove the wrapper then. Not sure what to do about the new timeout errors I'm seeing but I ssume these must only get generated now if the datastore is in fact down for some reason? So I guess I'll need to test for datastore availability and return a nice error to my users if it's down now I saw example code for that somewhere google search here I come :) Thanks Richard On Feb 27, 5:52 am, Ikai L (Google) ika...@google.com wrote: App Engine actually automatically retries now: http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ... http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...Was this the functionality you were looking for? On Thu, Feb 25, 2010 at 12:01 PM, rpalmer68 rich...@thepalmers.com.auwrote: Hi everybody, I need some help as a newbie GAE coder please. I found this really helpful cookbook entry about handling datastore timeouts and have implemented it in my code; http://appengine-cookbook.appspot.com/recipe/autoretry-datastore-time... It's been working well and I've been getting timeout warnings and retries instead of Time out errors just fine until about the 9th Feb and then I started getting the following errors coming up in my logs every now a then; --- datastore timeout: operation took too long. Traceback (most recent call last): File /base/python_lib/versions/1/google/appengine/ext/webapp/ __init__.py, line 507, in __call__ handler.get(*groups) File / base/data/home/apps/avi-web2/3.340039246064113396/online.py, line 188, in get count=q.count(2) File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 1585, in count result = raw_query.Count(limit=limit, rpc=rpc) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1211, in Count raise _ToDatastoreError(err) Timeout: datastore timeout: operation took too long. - Can anybody help me trap these errors using the code in the cookbook please? Many thanks Richard -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscrib...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Ikai Lan Developer Programs Engineer, Google App Enginehttp://googleappengine.blogspot.com|http://twitter.com/app_engine- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Datastore timeout: operation took too long.
Hi all, I also had similar issues, with a recent deployed application being used with a Google Apps account. I was surprised to see timeout errors in simple requests (insert/ delete), with a database with less than 10,000 rows. I was wondering how to imagine the whole scalability concept if timeouts become bottleneck from start... The worse I have noticed is that the timeout sometimes actually performs the action I requested (well, actually performing like a usual timeout error), but that complicates how I should handle the data. Can I just rely on the method is_saved() to avoid unnecessary retry if timeout cases happen? If anyone has created a wrap of db.Model with this implementation, please lead the way... Bruno On May 22, 10:04 pm, johntray john.tur...@gmail.com wrote: Has anyone suggested modifying db.get(), db.put(), and db.delete() to include an optional argument specifying a number-of-retries-on- timeout? I can wrap these functions in my own logic, but I would think nearly every application could use this. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Datastore timeout: operation took too long.
Hi Amir, Occasional datastore timeouts are expected to occur even in normal operation. It's up to you to handle them and react appropriately - for example, by retrying the operation. How often are you seeing this? -Nick Johnson 2009/5/22 Amir Michail amich...@gmail.com: Hello, Anyone else getting this exception? Amir --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Datastore timeout: operation took too long.
Has anyone suggested modifying db.get(), db.put(), and db.delete() to include an optional argument specifying a number-of-retries-on- timeout? I can wrap these functions in my own logic, but I would think nearly every application could use this. On May 22, 5:31 am, Nick Johnson (Google) nick.john...@google.com wrote: Hi Amir, Occasional datastore timeouts are expected to occur even in normal operation. It's up to you to handle them and react appropriately - for example, by retrying the operation. How often are you seeing this? -Nick Johnson 2009/5/22 Amir Michail amich...@gmail.com: Hello, Anyone else getting this exception? Amir --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: datastore timeout every time - on reads, not writes
I'm not sure, but it seems both
alerts = Alert.all().filter('expires = ', datetime.datetime.now())
and
alerts = Alert.all().filter('expires = ', datetime.datetime.now()).fetch(1000)
should be the same, since according to documents, app engine only
return the first 1000 records.
On Fri, May 1, 2009 at 1:36 PM, tayknight taykni...@gmail.com wrote:
I figured out that I needed to do a
alerts = Alert.all().filter('expires = ', datetime.datetime.now
()).fetch(1000)
Apparently it is faster to do a fetch() than iterate over the values.
On Apr 30, 7:28 pm, tayknight taykni...@gmail.com wrote:
Data is returned in development almost instantly. In production, the
error is returned after about 4 seconds. I get the datastore error
long before 30 seconds.
On Apr 29, 9:08 am, Liang Zhao alpha@gmail.com wrote:
Each request can only run 30 seconds in server side,
but in development server, there is no limitation on it...
On Wed, Apr 29, 2009 at 11:56 PM, tayknight taykni...@gmail.com wrote:
And, I should add, this works perfecty (and quickly) from the
development server's datastore.
On Apr 29, 8:31 am, tayknight taykni...@gmail.com wrote:
I have a problem. I'm getting datastore timeouts when doing reads. The
code finished about 5% of the time. The code looks like:
alerts = Alert.all().filter('expires = ', datetime.datetime.now())
# ge active alerts
for alert in alerts:
#get the db.Keys from the ListProperty
zones = ZoneMaster.get(alert.zones)
for zone in zones:
if zone:
#get the users for this zone
if zone.siteusers:
us = SiteUser.get(zone.siteusers)
for u in us:
if u:
self.response.out.write(u.name + 'br /')
The Model looks like:
class Alert(db.Model):
effective = db.DateTimeProperty()
expires = db.DateTimeProperty()
zones = db.ListProperty(db.Key)
class ZoneMaster(db.Model):
siteusers = db.ListProperty(db.Key)
class SiteUser(db.Model):
name = db.StringProperty()
zone = db.ReferenceProperty(ZoneMaster)
This code is repeatably timing out with a Timeout: datastore timeout:
operation took too long. error.
I'm not doing any writes. All the reads are by key (that come from a
ListProperty). Why would this be timing out?
Thanks.
--
Cheers!
Liang Zhao- Hide quoted text -
- Show quoted text -
--
Cheers!
Liang Zhao
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---
[google-appengine] Re: datastore timeout every time - on reads, not writes
On May 1, 12:28 pm, Liang Zhao alpha@gmail.com wrote:
I'm not sure, but it seems both
alerts = Alert.all().filter('expires = ', datetime.datetime.now())
and
alerts = Alert.all().filter('expires = ',
datetime.datetime.now()).fetch(1000)
should be the same, since according to documents, app engine only
return the first 1000 records.
Fetching the records as a batch and then doing stuff with them is
faster than treating a db.Query object as an iterable.
On the other hand, fetch(1000) is fairly likely to get you a datastore
timeout, depending on your data.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---
[google-appengine] Re: datastore timeout every time - on reads, not writes
Each request can only run 30 seconds in server side,
but in development server, there is no limitation on it...
On Wed, Apr 29, 2009 at 11:56 PM, tayknight taykni...@gmail.com wrote:
And, I should add, this works perfecty (and quickly) from the
development server's datastore.
On Apr 29, 8:31 am, tayknight taykni...@gmail.com wrote:
I have a problem. I'm getting datastore timeouts when doing reads. The
code finished about 5% of the time. The code looks like:
alerts = Alert.all().filter('expires = ', datetime.datetime.now())
# ge active alerts
for alert in alerts:
#get the db.Keys from the ListProperty
zones = ZoneMaster.get(alert.zones)
for zone in zones:
if zone:
#get the users for this zone
if zone.siteusers:
us = SiteUser.get(zone.siteusers)
for u in us:
if u:
self.response.out.write(u.name + 'br /')
The Model looks like:
class Alert(db.Model):
effective = db.DateTimeProperty()
expires = db.DateTimeProperty()
zones = db.ListProperty(db.Key)
class ZoneMaster(db.Model):
siteusers = db.ListProperty(db.Key)
class SiteUser(db.Model):
name = db.StringProperty()
zone = db.ReferenceProperty(ZoneMaster)
This code is repeatably timing out with a Timeout: datastore timeout:
operation took too long. error.
I'm not doing any writes. All the reads are by key (that come from a
ListProperty). Why would this be timing out?
Thanks.
--
Cheers!
Liang Zhao
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---
[google-appengine] Re: datastore timeout every time - on reads, not writes
Data is returned in development almost instantly. In production, the
error is returned after about 4 seconds. I get the datastore error
long before 30 seconds.
On Apr 29, 9:08 am, Liang Zhao alpha@gmail.com wrote:
Each request can only run 30 seconds in server side,
but in development server, there is no limitation on it...
On Wed, Apr 29, 2009 at 11:56 PM, tayknight taykni...@gmail.com wrote:
And, I should add, this works perfecty (and quickly) from the
development server's datastore.
On Apr 29, 8:31 am, tayknight taykni...@gmail.com wrote:
I have a problem. I'm getting datastore timeouts when doing reads. The
code finished about 5% of the time. The code looks like:
alerts = Alert.all().filter('expires = ', datetime.datetime.now())
# ge active alerts
for alert in alerts:
#get the db.Keys from the ListProperty
zones = ZoneMaster.get(alert.zones)
for zone in zones:
if zone:
#get the users for this zone
if zone.siteusers:
us = SiteUser.get(zone.siteusers)
for u in us:
if u:
self.response.out.write(u.name + 'br /')
The Model looks like:
class Alert(db.Model):
effective = db.DateTimeProperty()
expires = db.DateTimeProperty()
zones = db.ListProperty(db.Key)
class ZoneMaster(db.Model):
siteusers = db.ListProperty(db.Key)
class SiteUser(db.Model):
name = db.StringProperty()
zone = db.ReferenceProperty(ZoneMaster)
This code is repeatably timing out with a Timeout: datastore timeout:
operation took too long. error.
I'm not doing any writes. All the reads are by key (that come from a
ListProperty). Why would this be timing out?
Thanks.
--
Cheers!
Liang Zhao- Hide quoted text -
- Show quoted text -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---
[google-appengine] Re: datastore timeout every time - on reads, not writes
I figured out that I needed to do a
alerts = Alert.all().filter('expires = ', datetime.datetime.now
()).fetch(1000)
Apparently it is faster to do a fetch() than iterate over the values.
On Apr 30, 7:28 pm, tayknight taykni...@gmail.com wrote:
Data is returned in development almost instantly. In production, the
error is returned after about 4 seconds. I get the datastore error
long before 30 seconds.
On Apr 29, 9:08 am, Liang Zhao alpha@gmail.com wrote:
Each request can only run 30 seconds in server side,
but in development server, there is no limitation on it...
On Wed, Apr 29, 2009 at 11:56 PM, tayknight taykni...@gmail.com wrote:
And, I should add, this works perfecty (and quickly) from the
development server's datastore.
On Apr 29, 8:31 am, tayknight taykni...@gmail.com wrote:
I have a problem. I'm getting datastore timeouts when doing reads. The
code finished about 5% of the time. The code looks like:
alerts = Alert.all().filter('expires = ', datetime.datetime.now())
# ge active alerts
for alert in alerts:
#get the db.Keys from the ListProperty
zones = ZoneMaster.get(alert.zones)
for zone in zones:
if zone:
#get the users for this zone
if zone.siteusers:
us = SiteUser.get(zone.siteusers)
for u in us:
if u:
self.response.out.write(u.name + 'br /')
The Model looks like:
class Alert(db.Model):
effective = db.DateTimeProperty()
expires = db.DateTimeProperty()
zones = db.ListProperty(db.Key)
class ZoneMaster(db.Model):
siteusers = db.ListProperty(db.Key)
class SiteUser(db.Model):
name = db.StringProperty()
zone = db.ReferenceProperty(ZoneMaster)
This code is repeatably timing out with a Timeout: datastore timeout:
operation took too long. error.
I'm not doing any writes. All the reads are by key (that come from a
ListProperty). Why would this be timing out?
Thanks.
--
Cheers!
Liang Zhao- Hide quoted text -
- Show quoted text -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---
[google-appengine] Re: datastore timeout every time - on reads, not writes
And, I should add, this works perfecty (and quickly) from the
development server's datastore.
On Apr 29, 8:31 am, tayknight taykni...@gmail.com wrote:
I have a problem. I'm getting datastore timeouts when doing reads. The
code finished about 5% of the time. The code looks like:
alerts = Alert.all().filter('expires = ', datetime.datetime.now())
# ge active alerts
for alert in alerts:
#get the db.Keys from the ListProperty
zones = ZoneMaster.get(alert.zones)
for zone in zones:
if zone:
#get the users for this zone
if zone.siteusers:
us = SiteUser.get(zone.siteusers)
for u in us:
if u:
self.response.out.write(u.name + 'br /')
The Model looks like:
class Alert(db.Model):
effective = db.DateTimeProperty()
expires = db.DateTimeProperty()
zones = db.ListProperty(db.Key)
class ZoneMaster(db.Model):
siteusers = db.ListProperty(db.Key)
class SiteUser(db.Model):
name = db.StringProperty()
zone = db.ReferenceProperty(ZoneMaster)
This code is repeatably timing out with a Timeout: datastore timeout:
operation took too long. error.
I'm not doing any writes. All the reads are by key (that come from a
ListProperty). Why would this be timing out?
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---
[google-appengine] Re: DataStore timeout
I am experiencing similar problems... I know AppEngine is still pretty young, but I don't understand the high amount of dropped connections and internal errors following these timeouts. Isn't the platform supposed to be scaleable? It doesn't seem very much so... My old mysql-database could pull much more, much faster, without dropping connections, under high load. On Apr 7, 4:20 am, campos huwen...@gmail.com wrote: I had the same problem since couple of days before. It all worked fine previously. My app has a somewhat high frequency, about 30 request/ sec. Is that the cause? How to solve it? On Apr 5, 3:56 pm, cc c...@gamegiants.net wrote: We are seeing the same issue today. No problem in the past. Somebody tweaked something! On Apr 3, 5:31 am, DarkCoiote darkcoi...@gmail.com wrote: Getting a bad number of datastore timeout... and the operation is 'simple', is a put in simple model;... Traceback (most recent call last): File /base/python_lib/versions/1/google/appengine/ext/webapp/ __init__.py, line 501, in __call__ handler.get(*groups) File /base/data/home/apps/naval-war/1.332510333196150921/main.py, line 218, in get person.put() File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 669, in put return datastore.Put(self._entity) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 166, in Put raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1965, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout person model: class Person(db.Model): id = db.StringProperty() score = db.IntegerProperty(default=0) currentFleet = db.IntegerProperty(default=0) availableShots = db.IntegerProperty(default=0) maxShots = db.IntegerProperty(default=0) shipsSunk = db.ListProperty(int,verbose_name=Sunken ships list, default=[0,0,0,0,0]) shipsLost = db.ListProperty(int,verbose_name=Lost ships list, default=[0,0,0,0,0]) lastAccess = db.DateTimeProperty(auto_now_add=True) see... no references or anything complicated any tips on how to reduce the number of datastore timeouts?? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore timeout
I'm pretty sure they're not being made that rapidly... the rate is only high if the user keep hitting 'refresh'... but I guess that is not the case... You said something about parent, but my models doesn't have any references, so I guess it is not the case too, is it? Thank you! On Apr 3, 10:14 pm, Jeff S j...@google.com wrote: Hi DarkCoiote, How rapidly are puts being made on a single entity? There is a write speed limit for a single entity or entity-group so if these puts are being made against the same person, or if puts are being made to objects which share the same parent, the put operations may queue up and eventually time out. Does this seem like it could be the issue? Thank you, Jeff On Apr 3, 5:31 am, DarkCoiote darkcoi...@gmail.com wrote: Getting a bad number of datastore timeout... and the operation is 'simple', is a put in simple model;... Traceback (most recent call last): File /base/python_lib/versions/1/google/appengine/ext/webapp/ __init__.py, line 501, in __call__ handler.get(*groups) File /base/data/home/apps/naval-war/1.332510333196150921/main.py, line 218, in get person.put() File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 669, in put return datastore.Put(self._entity) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 166, in Put raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1965, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout person model: class Person(db.Model): id = db.StringProperty() score = db.IntegerProperty(default=0) currentFleet = db.IntegerProperty(default=0) availableShots = db.IntegerProperty(default=0) maxShots = db.IntegerProperty(default=0) shipsSunk = db.ListProperty(int,verbose_name=Sunken ships list, default=[0,0,0,0,0]) shipsLost = db.ListProperty(int,verbose_name=Lost ships list, default=[0,0,0,0,0]) lastAccess = db.DateTimeProperty(auto_now_add=True) see... no references or anything complicated any tips on how to reduce the number of datastore timeouts?? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore timeout
I had the same problem since couple of days before. It all worked fine previously. My app has a somewhat high frequency, about 30 request/ sec. Is that the cause? How to solve it? On Apr 5, 3:56 pm, cc c...@gamegiants.net wrote: We are seeing the same issue today. No problem in the past. Somebody tweaked something! On Apr 3, 5:31 am, DarkCoiote darkcoi...@gmail.com wrote: Getting a bad number of datastore timeout... and the operation is 'simple', is a put in simple model;... Traceback (most recent call last): File /base/python_lib/versions/1/google/appengine/ext/webapp/ __init__.py, line 501, in __call__ handler.get(*groups) File /base/data/home/apps/naval-war/1.332510333196150921/main.py, line 218, in get person.put() File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 669, in put return datastore.Put(self._entity) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 166, in Put raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1965, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout person model: class Person(db.Model): id = db.StringProperty() score = db.IntegerProperty(default=0) currentFleet = db.IntegerProperty(default=0) availableShots = db.IntegerProperty(default=0) maxShots = db.IntegerProperty(default=0) shipsSunk = db.ListProperty(int,verbose_name=Sunken ships list, default=[0,0,0,0,0]) shipsLost = db.ListProperty(int,verbose_name=Lost ships list, default=[0,0,0,0,0]) lastAccess = db.DateTimeProperty(auto_now_add=True) see... no references or anything complicated any tips on how to reduce the number of datastore timeouts?? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore timeout
We are seein g the same issue today. No problem in the past. Somebody tweaked something! On Apr 3, 6:14 pm, Jeff S j...@google.com wrote: Hi DarkCoiote, How rapidly are puts being made on a single entity? There is a write speed limit for a single entity or entity-group so if these puts are being made against the same person, or if puts are being made to objects which share the same parent, the put operations may queue up and eventually time out. Does this seem like it could be the issue? Thank you, Jeff On Apr 3, 5:31 am, DarkCoiote darkcoi...@gmail.com wrote: Getting a bad number of datastore timeout... and the operation is 'simple', is a put in simple model;... Traceback (most recent call last): File /base/python_lib/versions/1/google/appengine/ext/webapp/ __init__.py, line 501, in __call__ handler.get(*groups) File /base/data/home/apps/naval-war/1.332510333196150921/main.py, line 218, in get person.put() File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 669, in put return datastore.Put(self._entity) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 166, in Put raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1965, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout person model: class Person(db.Model): id = db.StringProperty() score = db.IntegerProperty(default=0) currentFleet = db.IntegerProperty(default=0) availableShots = db.IntegerProperty(default=0) maxShots = db.IntegerProperty(default=0) shipsSunk = db.ListProperty(int,verbose_name=Sunken ships list, default=[0,0,0,0,0]) shipsLost = db.ListProperty(int,verbose_name=Lost ships list, default=[0,0,0,0,0]) lastAccess = db.DateTimeProperty(auto_now_add=True) see... no references or anything complicated any tips on how to reduce the number of datastore timeouts?? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore timeout
We are seeing the same issue today. No problem in the past. Somebody tweaked something! On Apr 3, 5:31 am, DarkCoiote darkcoi...@gmail.com wrote: Getting a bad number of datastore timeout... and the operation is 'simple', is a put in simple model;... Traceback (most recent call last): File /base/python_lib/versions/1/google/appengine/ext/webapp/ __init__.py, line 501, in __call__ handler.get(*groups) File /base/data/home/apps/naval-war/1.332510333196150921/main.py, line 218, in get person.put() File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 669, in put return datastore.Put(self._entity) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 166, in Put raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1965, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout person model: class Person(db.Model): id = db.StringProperty() score = db.IntegerProperty(default=0) currentFleet = db.IntegerProperty(default=0) availableShots = db.IntegerProperty(default=0) maxShots = db.IntegerProperty(default=0) shipsSunk = db.ListProperty(int,verbose_name=Sunken ships list, default=[0,0,0,0,0]) shipsLost = db.ListProperty(int,verbose_name=Lost ships list, default=[0,0,0,0,0]) lastAccess = db.DateTimeProperty(auto_now_add=True) see... no references or anything complicated any tips on how to reduce the number of datastore timeouts?? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore timeout
Hi DarkCoiote, How rapidly are puts being made on a single entity? There is a write speed limit for a single entity or entity-group so if these puts are being made against the same person, or if puts are being made to objects which share the same parent, the put operations may queue up and eventually time out. Does this seem like it could be the issue? Thank you, Jeff On Apr 3, 5:31 am, DarkCoiote darkcoi...@gmail.com wrote: Getting a bad number of datastore timeout... and the operation is 'simple', is a put in simple model;... Traceback (most recent call last): File /base/python_lib/versions/1/google/appengine/ext/webapp/ __init__.py, line 501, in __call__ handler.get(*groups) File /base/data/home/apps/naval-war/1.332510333196150921/main.py, line 218, in get person.put() File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 669, in put return datastore.Put(self._entity) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 166, in Put raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1965, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout person model: class Person(db.Model): id = db.StringProperty() score = db.IntegerProperty(default=0) currentFleet = db.IntegerProperty(default=0) availableShots = db.IntegerProperty(default=0) maxShots = db.IntegerProperty(default=0) shipsSunk = db.ListProperty(int,verbose_name=Sunken ships list, default=[0,0,0,0,0]) shipsLost = db.ListProperty(int,verbose_name=Lost ships list, default=[0,0,0,0,0]) lastAccess = db.DateTimeProperty(auto_now_add=True) see... no references or anything complicated any tips on how to reduce the number of datastore timeouts?? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore Timeout !
I am also getting the same error. I have made no change in the code since 4-5 days back. GAE just released a new SDK, any change in the request timeout? I am sure my db size is not that big to cause such an error Any help?? On Sep 6, 4:36 pm, Sylvain [EMAIL PROTECTED] wrote: FYI : my appid = 'hordes' On 6 sep, 13:34, Sylvain [EMAIL PROTECTED] wrote: Since 1 hour, i've this error message : File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 779, in get_by_key_name return get(*keys) File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 974, in get entities = datastore.Get(keys) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 217, in Get raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1627, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout feed.put() File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 618, in put return datastore.Put(self._entity) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 162, in Put raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1627, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout -- Could you check this --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com 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 -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore Timeout !
I'm having the same problem, and it's not dependent on the size of the request -- I can't delete two entities, or save one session, or anything. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com 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 -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore Timeout !
No news... :( 6 hours down,... On 6 sep, 17:17, bin [EMAIL PROTECTED] wrote: I've got the same error since 4 hours ago, the datastore is completely inaccessible. On Sep 6, 9:52 pm, Nick Winter [EMAIL PROTECTED] wrote: I'm having the same problem, and it's not dependent on the size of the request -- I can't delete two entities, or save one session, or anything. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com 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 -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore Timeout !
It is becoming very long without news from this one... On 6 sep, 19:11, relistan [EMAIL PROTECTED] wrote: All-- I opened this defect report against the production systems:http://code.google.com/p/googleappengine/issues/detail?id=694 There was not one open already. I don't know if this is the proper procedure, but it seems like it needs to be reported somewhere. Cheers -K --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com 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 -~--~~~~--~~--~--~---
