1927: MariaDB: ER_CONNECTION_KILLED: Connection was killed
MySQLWhat does it mean?
MariaDB-specific: the running connection/thread was terminated by the server, the in-flight query was interrupted, and the client connection was dropped. This code does not exist in MySQL; there the same situation appears as 1317 (ER_QUERY_INTERRUPTED) when the query is interrupted, and as 2013 (Lost connection) on the client side when the connection drops.
Why does it happen?
An administrator or monitoring tool sending a KILL command; the server entering shutdown; idle connection limits in MariaDB such as idle_transaction_timeout/wait_timeout; or the server dropping the connection under resource pressure. Also seen during maintenance in cloud/proxy environments.
How to fix it
Investigate why the query was killed: SHOW PROCESSLIST and the slow query log for long-running queries; server maintenance/restart schedules; connection kill policies. Catch this error in the application and retry safely (if idempotent). Optimize and split long queries; use automatic reconnect in the connection pool.
More from this engine
- 2013Lost connection to MySQL server during query
- 1153Got a packet bigger than 'max_allowed_packet' bytes
- 1969MariaDB: Query execution was interrupted (max_statement_time exceeded)
- 1290ER_OPTION_PREVENTS_STATEMENT: running with the --read-only option
- 1836ER_READ_ONLY_MODE: Running in read-only mode
- 3819ER_CHECK_CONSTRAINT_VIOLATED: Check constraint is violated
- 1118ER_TOO_BIG_ROWSIZE: Row size too large