Details
-
Bug
-
Status: Needs Feedback (View Workflow)
-
Major
-
Resolution: Unresolved
-
11.8.6
-
None
-
None
Description
During physical MariaDB backup we observed spike in sql error logs like
root[root] @ [10.60.49.194] ERROR 1159: Got timeout reading communication packets : (null) |
2026-03-28 1:10:05 ERROR root[root] @ [10.60.49.194] ERROR 1205: Lock wait timeout exceeded; try restarting transaction : CREATE DATABASE IF NOT EXISTS replication_manager_schema |
2026-03-28 1:10:04 ERROR root[root] @ [10.60.49.194] ERROR 1159: Got timeout reading communication packets : (null) |
2026-03-28 1:10:04 ERROR root[root] @ [10.60.49.194] ERROR 1205: Lock wait timeout exceeded; try restarting transaction : CREATE DATABASE IF NOT EXISTS replication_manager_schema |
2026-03-28 1:10:03 ERROR root[root] @ [10.60.49.194] ERROR 1159: Got timeout reading communication packets : (null) |
2026-03-28 1:10:03 ERROR root[root] @ [10.60.49.194] ERROR 1205: Lock wait timeout exceeded; try restarting transaction : CREATE DATABASE IF NOT EXISTS replication_manager_schema |
2026-03-28 1:10:02 ERROR root[root] @ [10.60.49.194] ERROR 1159: Got timeout reading communication packets : (null) |
2026-03-28 1:10:02 ERROR root[root] @ [10.60.49.194] ERROR 1205: Lock wait timeout exceeded; try restarting transaction : CREATE DATABASE IF NOT EXISTS replication_manager_schema |
2026-03-28 1:00:02 ERROR root[root] @ [10.60.49.194] ERROR 1158: Got an error reading communication packets : (null) |
2026-03-28 1:00:02 ERROR root[root] @ [10.60.49.194] ERROR 1205: Lock wait timeout exceeded; try restarting transaction : CREATE DATABASE IF NOT EXISTS replication_manager_schema |
2026-03-28 1:00:02 ERROR root[root] @ [10.60.49.194] ERROR 1159: Got timeout reading communication packets : (null) |
The database already exist , it's not clear why such operation is not escalade read lock only after a first lookup if the schema does not exists