RE: Time Limit Exceeded Errors
We have a search utility library that we use to grab search results that works great. However, we have one M/R that has started failing on the runPaged() call. What’s more interesting is that the M/R uses this library multiple times, and succeeds on multiple calls, but continues to get failures on a transaction search. It just times out and returns the error that says something like “Search timed out, try scheduling your results to be sent to you… etc.”
More interesting is that our jobs are batched into reduce where this search utility is called. Some batches execute without any issue at all, while others fail out. The data sets where it’s failing are anywhere from a few hundred results to a few thousand, but nothing out of the ordinary compared to the other batches.
Logging getRemainingUsage there is ample usage left within the script, and with regards to time, it’s failing out after sitting on runPaged for maybe 10 minutes or so.
If anyone has any advice, it would be a big help. Here is the search library:
Saved searches have a limit of like 5 or 10 minutes before they time out irrespective of MR limitations. You’ll likely need to break up your search definition. Do you have complicated filters or columns? Can you put in a filter to segment the search by a date range or internalid?