1117978 - Search query reliably fails

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: General, defect)

Description

[Eric Ziegenhorn :ericz]

Searching bugzilla via the search box (or an awesomebar search query based on it) for "status.mozilla.org cert" without the quotes reliably gives me an error about a database connection which seems wrong.  The error text is:


Bugzilla has suffered an internal error:

DBD::mysql::db selectcol_arrayref failed: Lost connection to MySQL server during query [for Statement "SELECT bugs.bug_id AS bug_id, bugs.bug_status AS bug_status, bugs.priority AS priority, map_assigned_to.login_name AS assigned_to FROM bugs LEFT JOIN bug_group_map AS security_map ON bugs.bug_id = security_map.bug_id AND NOT ( security_map.group_id IN (20,19,31,10,9,8,170,149,151,150,119,69,84,35,74,75,158,32,6,42,26,89,96,181,113,76,186,187,178,177,180,179) ) LEFT JOIN cc AS security_cc ON bugs.bug_id = security_cc.bug_id AND security_cc.who = 436972 INNER JOIN profiles AS map_assigned_to ON bugs.assigned_to = map_assigned_to.userid INNER JOIN bug_status AS map_bug_status ON bugs.bug_status = map_bug_status.value INNER JOIN priority AS map_priority ON bugs.priority = map_priority.value LEFT JOIN bugs_fulltext AS bugs_fulltext_6 ON bugs.bug_id = bugs_fulltext_6.bug_id LEFT JOIN bugs_fulltext AS bugs_fulltext_14 ON bugs.bug_id = bugs_fulltext_14.bug_id WHERE bugs.creation_ts IS NOT NULL AND (security_map.group_id IS NULL OR (bugs.reporter_accessible = 1 AND bugs.reporter = 436972) OR (bugs.cclist_accessible = 1 AND security_cc.who IS NOT NULL) OR bugs.assigned_to = 436972 OR bugs.qa_contact = 436972) AND bugs.bug_status IN ('UNCONFIRMED','NEW','ASSIGNED','REOPENED') AND ( ( ( 1=2 OR 1=2 OR INSTR(COALESCE(bugs.alias, ''), 'status.mozilla.org') > 0 OR INSTR(bugs.short_desc, 'status.mozilla.org') > 0 OR INSTR(bugs.status_whiteboard, 'status.mozilla.org') > 0 OR MATCH(bugs_fulltext_6.comments_noprivate) AGAINST('\"status.mozilla.org\"' IN BOOLEAN MODE) OR MATCH(bugs_fulltext_6.short_desc) AGAINST('\"status.mozilla.org\"' IN BOOLEAN MODE) OR INSTR(COALESCE(bugs.cf_crash_signature, ''), 'status.mozilla.org') > 0 OR INSTR(COALESCE(bugs.bug_file_loc, ''), 'status.mozilla.org') > 0 ) ) AND ( ( 1=2 OR bugs.component_id IN (370,796,1990) OR INSTR(COALESCE(bugs.alias, ''), 'cert') > 0 OR INSTR(bugs.short_desc, 'cert') > 0 OR INSTR(bugs.status_whiteboard, 'cert') > 0 OR MATCH(bugs_fulltext_14.comments_noprivate) AGAINST('\"cert\"' IN BOOLEAN MODE) OR MATCH(bugs_fulltext_14.short_desc) AGAINST('\"cert\"' IN BOOLEAN MODE) OR INSTR(COALESCE(bugs.cf_crash_signature, ''), 'cert') > 0 ) ) ) GROUP BY bugs.bug_id ORDER BY map_bug_status.sortkey, map_bug_status.value, map_priority.sortkey, map_priority.value, assigned_to, bug_id LIMIT 500 "]

Comment 1

[Eric Ziegenhorn :ericz]

Poked a little more:

These searches work:
test.search
www.mozilla.com
status.

These searches fail:
status.mozilla.com
status.mozilla.org

Comment 2

[:glob ✱]

this error means "this search took so long, mysql terminated the query".

bugzilla has more than one "search box"; are you able to provide the search url?


my guess is you're using the search box in the header, and have the user preference "Include comments when performing quick searches" set to "On" (the default is Off).  the weirdness with regards to handling of different searches backs this up (mysql's fulltext searching, which is what is used for comment searching, can be .. interesting .. at times).


searching _all_ comments in bugzilla is currently slow.  experiments with using other systems to search comments have started (eg. elasticsearch), but i don't have an ETA on those i'm sorry.

Comment 3

[Eric Ziegenhorn :ericz]

Yes it appears to be the Quick Search box in the header that I'm using.  You're also right that I do have the pref on to search comments.  We're all good on closing this bug then, I just thought that if it timed out it'd say something to the effect of "took too long -- try a different query" rather than that lengthy error message.  Thanks for explaining!

Comment 4

[:glob ✱]

i fixed this by backporting bug 1089475 to bmo, with some bmo-specific code which catches a 'lost connection' error and replaces it with 'The database query took too long to complete and has been canceled'.

http://git.mozilla.org/?p=webtools/bmo/bugzilla.git;a=commitdiff;h=0ed20de47a3a320029123164b0d36a1e6cc0cbab [github]