Support query timeouts via `max_statement_time` or MYSLQI_ASYNC
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	epriestley
	Apr 21 2016, 6:21 PM

Description

See T10847. If MySQL hangs (e.g., because disk space is exhausted) our recovery behavior is very bad.

The max_statement_time / max_execution_time options introduced in MySQL 5.7.4, or client-side mechanisms via MYSLQI_ASYNC, would allow us to recover from this situation (at least, in web processes) far more gracefully.

Revisions and Commits

rPHU libphutil
	D15781	rPHU139d316c4484 Support query timeouts with mysqli on the client side
rP Phabricator
	D15799	rP0630fef9fc36 Prevent web queries from running for more than 30 seconds

Related Objects

Mentioned In: T10847: 30GB Phacility instance caused a series of cascading failures which left web services unreachable
Mentioned Here: T11044: Support partitioning application databases across multiple database hosts
T2383: Run PHP environment checks from CLI
D15781: Support query timeouts with mysqli on the client side
T10847: 30GB Phacility instance caused a series of cascading failures which left web services unreachable

Event Timeline

epriestley created this task.Apr 21 2016, 6:21 PM

Herald added subscribers: chad, eadler. · View Herald TranscriptApr 21 2016, 6:21 PM

epriestley claimed this task.Apr 21 2016, 6:21 PM

epriestley mentioned this in T10847: 30GB Phacility instance caused a series of cascading failures which left web services unreachable.Apr 21 2016, 6:53 PM

epriestley added a revision: D15781: Support query timeouts with mysqli on the client side.Apr 21 2016, 11:18 PM

D15781 is promising and it looks like we can do this purely on the client if it has relatively old PHP, without requiring relatively new MySQL and special configuration on the server.