Adding an index shouldn't cause reads to take longer, though it will add time to the writes. It's more likely that your adding of an index was simply a coincidence. Are you still seeing these datastore issues?
On Sat, Feb 6, 2010 at 5:11 AM, Jason Smith <j...@proven-corporation.com>wrote: > We have a cron job which fetches up to 1,000 entities based on a > timestamp--no transactions, no writes. It has been working for several > weeks. > > I recently added an index (the timestamp, plus a boolean). > Subsequently, the datastore is almost completely unresponsive with > these entities. The vast majority of the queries raise a Timeout > exception, always after exactly 4 seconds. It seems that I can hardly > query these entities at all, using any filter. > > I was under the impression that off-and-on timeouts are transient. But > this has been happening for nearly a day. Also I expected that once an > index is serving, no legal query could possibly time out always. > > I am concerned that I have an index or datastore issue. Does anybody > have any insights about 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-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@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 Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- 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.
