Hey Ananthakrishnan, While we are aware this can happen, as it has for other users in the past, and we commit ourselves daily to maintaining the uptime of our systems, I'm glad to hear that it is not consistent, and you have a retry logic. This is indeed a best practice for distributed systems which need to have a higher level of fault-tolerance and defensive programming (using incremental backoff, etc.) than traditional single-system applications.
Search API is a backend API service for App Engine, and it basically is a distributed system. Hence it can happen that one job is stuck, takes longer time to complete, and results in timeout. The exception only means that the particular request timed out. If you would like to experiment with different settings than a 10 second timeout, you can specify your desired timeout value <https://cloud.google.com/appengine/docs/java/javadoc/com/google/appengine/api/search/SearchServiceConfig.Builder#setDeadline-java.lang.Double-> using the setDeadline() method during building of the SearchService. I hope this response has been helpful - let me know if you have any further questions and I'll be happy to assist. Sincerely, Nick Cloud Platform Community Support On Thursday, April 14, 2016 at 4:10:52 AM UTC-4, Ananthakrishnan Venkatasubramanian wrote: > > Hey Nick, > > Thanks for your kind reply. Will keep an eye on this thread for further > updates. > > Regards, > Ananthakrishnan. > > On Thursday, April 14, 2016 at 5:21:45 AM UTC+5:30, Nick (Cloud Platform > Support) wrote: >> >> Hey Ananthakrishnan, >> >> This appears to be some kind of internal error, and is not something you >> can necessarily prevent as a developer. It appears it has happened in >> the past >> <https://groups.google.com/forum/#!msg/google-appengine/ETydrw1RJ6Y/jrx1zgyfCgAJ> >> >> and was related to an internal issue. I'll look into this and report back >> with any findings. >> >> Sincerely, >> >> Nick >> Cloud Platform Community Support >> >> On Tuesday, April 12, 2016 at 10:51:18 AM UTC-4, Ananthakrishnan >> Venkatasubramanian wrote: >>> >>> Hi, >>> >>> >>> We have an application developed using Java running in google appengine. >>> >>> >>> When AppEngine's Search API is accessed for querying the records, >>> sporadically we get the following exception (not always). But when we try >>> again it is responding with results. >>> >>> >>> Stacktrace : >>> Class : class com.google.appengine.api.search.SearchExceptionMessage : >>> Failed to complete request in 9498ms >>> >>> at >>> com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:355) >>> at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:96) >>> at >>> com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73) >>> at >>> com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32) >>> at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:506) >>> >>> >>> Please let us know what is the issue behind this failure and what's the >>> remedy for it. >>> >>> >>> Thanks in Advance. >>> >>> >>> Regards, >>> >>> Ananthakrishnan. >>> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2ee84546-3eee-4e4b-a4d1-e5e6afd337e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
