Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Incomplete
-
10.2.29
Description
I am noticing different behavior in mariadb 10.1 & 10.2 reg.connection aborts.
I noticed connection getting aborted after 7 minutes(wait_timeout) of any query execution. There are few random connection aborts happening in my application too. But I don't see this behavior(connection abort logs) happening in mariadb 10.1.
I am aware that the default value for variable "log_warnings" has been changed from 1 to 2 in MariaDB 10.2. But even with log_warnings value as 2 in MariaDB 10.1, I don't see connection aborts happening.
For eg. In below query connection Id : 2218 is created
MariaDB [dummy]> show global variables like '%log%'; |
ERROR 2006 (HY000): MySQL server has gone away |
No connection. Trying to reconnect...
|
Connection id: 2218 |
Current database: dummy
|
From general query logs, the query executed time is 11:53:15
201222 11:53:15 6 Query SHOW MASTER STATUS |
6 Query SHOW SLAVE STATUS |
6 Query UPDATE `oam`.`heartbeat` SET ts='2020-12-22T11:53:15.000830', file='mariadb-bin.000001', position='58352014', relay_master_log_file=NULL, exec_master_log_pos=NULL WHERE server_id='1' |
2218 Connect root@localhost as anonymous on dummy |
2218 Query show databases |
2218 Query show tables |
2218 Field List mytable |
2218 Query show global variables like '%wait%' |
From Error logs, the connection closed at 12:00:16
2020-12-22 12:00:16 140673402672896 [Warning] Aborted connection 2218 to db: 'dummy' user: 'root' host: 'localhost' (Got timeout reading communication packets) |
wait_timeout is set to 7mins(420s)
MariaDB [dummy]> show global variables like 'wait_timeout%'; |
+---------------+-------+
|
| Variable_name | Value |
|
+---------------+-------+
|
| wait_timeout | 420 | |
+---------------+-------+
|
1 row in set (0.01 sec) |
I could see the same behavior happening for any query execution (Connection aborting after 7mins) in MariaDB 10.2 but it is not happening in 10.1 even when the log_warnings level set to 2