Closed
Bug 1937196
Opened 10 months ago
Closed 5 months ago
Set a maximum timeout value for MySQL depending on whether the user is logged in or not
Categories
(bugzilla.mozilla.org :: Infrastructure, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dkl, Assigned: glob)
Details
Attachments
(1 file)
We should be able to set a maximum timeout value per session for all SQL statements executed. We will have two configurable values in the params, one for authenticated users and one for unauthenticated users. If either is set to 0 then there is no timeout as we have now. This is mainly to help keep the replica MySQL instances from getting bogged down with very long running queries which degrades the experience for others.
From MySQL docs:
max_execution_time applies as follows:
The global max_execution_time value provides the default for the session value for new connections. The session value applies to SELECT executions executed within the session that include no MAX_EXECUTION_TIME(N) optimizer hint or for which N is 0.
max_execution_time applies to read-only SELECT statements. Statements that are not read only are those that invoke a stored function that modifies data as a side effect.
max_execution_time is ignored for SELECT statements in stored programs.
Comment 1•5 months ago
|
||
Comment 2•5 months ago
|
||
Authored by https://github.com/globau
https://github.com/mozilla-bteam/bmo/commit/fda243288f65b4150897440148bac135ec5c0ef8
[master] Bug 1937196 - Add database timeouts to search queries
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•