706967 - [traceback] [prod] Exception: SearchError: Query has timed out.

Status: RESOLVED WORKSFORME

Description

[Matt Brandt [:mbrandt]]

Recently we've gotten a few similar tracebacks of this nature whereas historically we haven't. I'm unable to reproduce this traceback but wanted to raise it for further investigation.

Traceback (most recent call last):

 File "/data/www/django/input.mozilla.com/reporter/vendor/src/django/django/core/handlers/base.py", line 111, in get_response
   response = callback(request, *callback_args, **callback_kwargs)

 File "/data/www/django/input.mozilla.com/reporter/vendor/src/django/django/contrib/syndication/views.py", line 34, in __call__
   obj = self.get_object(request, *args, **kwargs)

 File "/data/www/django/input.mozilla.com/reporter/apps/search/views.py", line 103, in get_object
   data = dict(opinions=_get_results(request)[0], request=request)

 File "/data/www/django/input.mozilla.com/reporter/apps/search/views.py", line 41, in _get_results
   opinions = c.query(query, **search_opts)

 File "/data/www/django/input.mozilla.com/reporter/apps/search/client.py", line 218, in query
   raise SearchError(_("Query has timed out."))

SearchError: Query has timed out.

Comment 1

[Matt Brandt [:mbrandt]]

These are still trickling in for en-US/search/atom?product=firefox&version=--&nocache-1323748561

Can we patch this or if it's a non-issue have these caught by arecibo to reduce the traceback email?

Comment 2

[[:Cww]]

Input rewrite seems to have addressed search performance.