Page MenuHomePhabricator

Provide users a hint that "KILL <process>" is a possible source of connection loss
ClosedPublic

Authored by epriestley on Oct 24 2018, 5:42 PM.
Tags
None
Referenced Files
F17628442: D19756.diff
Thu, Jul 10, 7:31 AM
Unknown Object (File)
Tue, Jun 17, 4:29 PM
Unknown Object (File)
Jun 3 2025, 10:28 PM
Unknown Object (File)
Jun 2 2025, 2:09 PM
Unknown Object (File)
May 28 2025, 4:16 PM
Unknown Object (File)
May 10 2025, 3:48 AM
Unknown Object (File)
May 7 2025, 5:20 AM
Unknown Object (File)
May 7 2025, 3:58 AM
Subscribers
None

Details

Summary

Ref T13210. See PHI943. When a query fails due to connection loss we currently suggest "wait_timeout" and "max_allowed_packet", but something KILL'ing us also causes this outcome. Add that as a suggestion.

Test Plan

KILL'd a lock three times, got:

$ php -f lock.php 
[2018-10-24 10:40:29] EXCEPTION: (AphrontConnectionLostQueryException) #2006: MySQL server has gone away

This error may occur if your configured MySQL "wait_timeout" or "max_allowed_packet" values are too small. This may also indicate that something used the MySQL "KILL <process>" command to kill the connection running the query. at [<phutil>/src/aphront/storage/connection/mysql/AphrontBaseMySQLDatabaseConnection.php:304]
...

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable