DataStore timeout

54 views
Skip to first unread message

DarkCoiote

unread,
Apr 3, 2009, 8:31:32 AM4/3/09
to Google App Engine
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??

Jeff S

unread,
Apr 3, 2009, 9:14:55 PM4/3/09
to Google App Engine
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
Message has been deleted

cc

unread,
Apr 5, 2009, 3:56:42 PM4/5/09
to Google App Engine
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:

DarkCoiote

unread,
Apr 6, 2009, 9:07:09 AM4/6/09
to Google App Engine
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!

campos

unread,
Apr 6, 2009, 10:20:29 PM4/6/09
to Google App Engine
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?

baytiger

unread,
Apr 11, 2009, 5:31:32 AM4/11/09
to Google App Engine
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.
Reply all
Reply to author
Forward
0 new messages