[google-appengine] Re: SearchException - Failed to complete request

2016-08-15 Thread 'Nick (Cloud Platform Support)' via Google App Engine 
Hey John,

Glad to hear things worked out, and that the effects were ephemeral at any 
rate. Best of luck going forward!

Cheers,

Nick
Cloud Platform Community Support

On Saturday, August 13, 2016 at 4:43:45 AM UTC-4, John Wieczorek wrote:
>
> Hi Nick,
>
> Here is a belated followup. I do not know why the production effects were 
> seen, but they were ephemeral. The index I was loading also eventually 
> became responsive, though many searches continued to fail. In the process I 
> learned how to improve the search efficiency by changing the data type to 
> Atom fields wherever reasonably possible. This improved search execution to 
> the point where it was not even necessary to bump up the instance class nor 
> to change the default url fetch deadline.
>
> Thanks for your responsiveness when the issue arose.
>
>
> On Tuesday, July 19, 2016 at 10:57:00 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> A link to the Public Issue Tracker for App Engine 
>> , left out of the 
>> last message.
>>
>> On Monday, July 18, 2016 at 5:13:35 PM UTC-4, John Wieczorek wrote:
>>>
>>> I am have been experiencing symptoms similar to those described here and 
>>> on the set of postings in the past 
>>> 
>>>  as 
>>> mentioned earlier in this thread. There are no reports of abnormal 
>>> operations, but my index has essentially become non-functional, with 
>>> timeouts when searching, or even deleting. I do use retry logic, but the 
>>> queries are failing persistently. The problems began at 
>>> 2016-07-18T14:47:10Z 
>>> and have persisted since. 
>>>
>>> Actually, I have just checked a production system that has been 
>>> functional until now that uses a different index from the one I was having 
>>> trouble with, and it too is timing out consistently for certain types of 
>>> queries that did not fail in the past.
>>>
>>> Any recommendations for how to find out what might be causing this, and 
>>> how to recover from this situation?
>>>
>>> On Thursday, April 14, 2016 at 7:18:33 PM UTC+2, Nick (Cloud Platform 
>>> Support) wrote:

 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 
 
  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 
>> 
>>  
>> 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 :

[google-appengine] Re: SearchException - Failed to complete request

2016-08-13 Thread John Wieczorek 
Hi Nick,

Here is a belated followup. I do not know why the production effects were 
seen, but they were ephemeral. The index I was loading also eventually 
became responsive, though many searches continued to fail. In the process I 
learned how to improve the search efficiency by changing the data type to 
Atom fields wherever reasonably possible. This improved search execution to 
the point where it was not even necessary to bump up the instance class nor 
to change the default url fetch deadline.

Thanks for your responsiveness when the issue arose.


On Tuesday, July 19, 2016 at 10:57:00 PM UTC+2, Nick (Cloud Platform 
Support) wrote:
>
> A link to the Public Issue Tracker for App Engine 
> , left out of the 
> last message.
>
> On Monday, July 18, 2016 at 5:13:35 PM UTC-4, John Wieczorek wrote:
>>
>> I am have been experiencing symptoms similar to those described here and 
>> on the set of postings in the past 
>> 
>>  as 
>> mentioned earlier in this thread. There are no reports of abnormal 
>> operations, but my index has essentially become non-functional, with 
>> timeouts when searching, or even deleting. I do use retry logic, but the 
>> queries are failing persistently. The problems began at 2016-07-18T14:47:10Z 
>> and have persisted since. 
>>
>> Actually, I have just checked a production system that has been 
>> functional until now that uses a different index from the one I was having 
>> trouble with, and it too is timing out consistently for certain types of 
>> queries that did not fail in the past.
>>
>> Any recommendations for how to find out what might be causing this, and 
>> how to recover from this situation?
>>
>> On Thursday, April 14, 2016 at 7:18:33 PM UTC+2, Nick (Cloud Platform 
>> Support) wrote:
>>>
>>> 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 
>>> 
>>>  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 
> 
>  
> 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)
>>

[google-appengine] Re: SearchException - Failed to complete request

2016-07-19 Thread 'Nick (Cloud Platform Support)' via Google App Engine 
A link to the Public Issue Tracker for App Engine 
, left out of the 
last message.

On Monday, July 18, 2016 at 5:13:35 PM UTC-4, John Wieczorek wrote:
>
> I am have been experiencing symptoms similar to those described here and 
> on the set of postings in the past 
> 
>  as 
> mentioned earlier in this thread. There are no reports of abnormal 
> operations, but my index has essentially become non-functional, with 
> timeouts when searching, or even deleting. I do use retry logic, but the 
> queries are failing persistently. The problems began at 2016-07-18T14:47:10Z 
> and have persisted since. 
>
> Actually, I have just checked a production system that has been functional 
> until now that uses a different index from the one I was having trouble 
> with, and it too is timing out consistently for certain types of queries 
> that did not fail in the past.
>
> Any recommendations for how to find out what might be causing this, and 
> how to recover from this situation?
>
> On Thursday, April 14, 2016 at 7:18:33 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> 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 
>> 
>>  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 
 
  
 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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this

[google-appengine] Re: SearchException - Failed to complete request

2016-07-19 Thread 'Nick (Cloud Platform Support)' via Google App Engine 
Hey John,

If you believe you've encountered a production issue, which this sounds 
like, you should file a Public Issue Tracker report. You can also get a 
support package for more on-demand response times, but we are very diligent 
with monitoring the Public Issue Trackers at any rate, and you should see a 
response quickly. Provide you project ID, the name of the indexes, and as 
much information as possible. Post the issue here once you've made it, so 
that I can take a look as well - I'm happy to help.

Regards,

Nick
Cloud Platform Community Support

On Monday, July 18, 2016 at 5:13:35 PM UTC-4, John Wieczorek wrote:
>
> I am have been experiencing symptoms similar to those described here and 
> on the set of postings in the past 
> 
>  as 
> mentioned earlier in this thread. There are no reports of abnormal 
> operations, but my index has essentially become non-functional, with 
> timeouts when searching, or even deleting. I do use retry logic, but the 
> queries are failing persistently. The problems began at 2016-07-18T14:47:10Z 
> and have persisted since. 
>
> Actually, I have just checked a production system that has been functional 
> until now that uses a different index from the one I was having trouble 
> with, and it too is timing out consistently for certain types of queries 
> that did not fail in the past.
>
> Any recommendations for how to find out what might be causing this, and 
> how to recover from this situation?
>
> On Thursday, April 14, 2016 at 7:18:33 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> 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 
>> 
>>  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 
 
  
 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,
>
>

[google-appengine] Re: SearchException - Failed to complete request

2016-07-18 Thread John Wieczorek 
I am have been experiencing symptoms similar to those described here and on 
the set of postings in the past 

 as 
mentioned earlier in this thread. There are no reports of abnormal 
operations, but my index has essentially become non-functional, with 
timeouts when searching, or even deleting. I do use retry logic, but the 
queries are failing persistently. The problems began at 2016-07-18T14:47:10Z 
and have persisted since. 

Actually, I have just checked a production system that has been functional 
until now that uses a different index from the one I was having trouble 
with, and it too is timing out consistently for certain types of queries 
that did not fail in the past.

Any recommendations for how to find out what might be causing this, and how 
to recover from this situation?

On Thursday, April 14, 2016 at 7:18:33 PM UTC+2, Nick (Cloud Platform 
Support) wrote:
>
> 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 
> 
>  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 
>>> 
>>>  
>>> 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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/21f62f23-f27f-4468-91a0-c1599d5c9a1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: SearchException - Failed to complete request

2016-04-15 Thread Ananthakrishnan Venkatasubramanian 
Hey Nick,

Will try your suggestion.

Thanks for the quick response :)

On Thursday, April 14, 2016 at 10:48:33 PM UTC+5:30, Nick (Cloud Platform 
Support) wrote:
>
> 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 
> 
>  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 
>>> 
>>>  
>>> 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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/9b76fbcf-587b-438a-9b68-0b57dd0e9a29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: SearchException - Failed to complete request

2016-04-14 Thread 'Nick (Cloud Platform Support)' via Google App Engine 
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 

 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 
>> 
>>  
>> 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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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.

[google-appengine] Re: SearchException - Failed to complete request

2016-04-14 Thread Ananthakrishnan Venkatasubramanian 
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 
> 
>  
> 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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/94e93511-c735-4f01-963f-0b793394005d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: SearchException - Failed to complete request

2016-04-13 Thread 'Nick (Cloud Platform Support)' via Google App Engine 
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 

 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/1f2ac40e-7457-45ad-a08c-c0e32c83d0ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.