Closed Bug 474037 Opened 16 years ago Closed 15 years ago

Each search on Socorro ends in connection interrupted

Categories

(Socorro :: General, task)

task
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: whimboo, Unassigned)

Details

Since a couple of days I'm not able to run searches against the database. Sometimes it has been working but really slow. Currently each search results in a "connection gets interrupted" error.

It can be seen when running topcrasher searches or searches like following on a given release:

http://crash-stats.mozilla.com/?do_query=1&product=Firefox&branch=1.9.1&version=Firefox%3A3.1b3pre&query_search=signature&query_type=contains&query=nsMenuItemIconX%3A%3AOnStopRequest%28imgIRequest*%2C+int%29&date=&range_value=1&range_unit=weeks

I have to stop with my crash analysis until this issue has been fixed. Please do it asap. A lot of people are affected by this mal-function. Thanks!
thanks for the cc:  agree 100%. Affecting more than just topcrash query.

this is occurring for me even in hours when I'd have thought there's not much activity/contention on crash-stats.  It's been at least a few days.  Perhaps more - can't tell because I wasn't using it much in the period -1 to -2 weeks ago.
Is this much different than bug 468405 or has that problem just gotten worse?
I would say it's different because performance is worse the last few days, compared to the prior month - in come cases for even trivial queries, nevermind reasonable ones.  

But can't say it's definitely the same as 468405 without knowing the underlying cause.
Sam, I filed it as a new bug because it started to happen lately. So something has been broken again. I'ld tend to not dupe the bug. Your bug is a general one which will not be solved by this bug. I just want to have back the search functionality.
This is fixed with the re-partitioning.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Not really. I did a test with the URL given in comment 0 and I still into a timeout.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
So, really, that's not "each search" failing, that's one, specific, search failing. In the case of the query in comment 0, you wouldn't want to search for that anyway. You'd want to search for "is exactly" since you put in the exact stack. That'd be this query:

http://crash-stats.mozilla.com/?do_query=1&product=Firefox&branch=1.9.1&version=Firefox%3A3.1b3pre&query_search=signature&query_type=exact&query=nsMenuItemIconX%3A%3AOnStopRequest(imgIRequest*%2C+int)&date=&range_value=1&range_unit=weeks
I filed bug 478043 to have a better default option to search for crashes. Lets mark this bug as verified. Thanks Sam for the hints!
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Verified fixed by using the "is exactly" option.
Status: RESOLVED → VERIFIED
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.