Page MenuHomePhabricator

Support an explicit connection timeout parameter for database connections
ClosedPublic

Authored by epriestley on Dec 8 2014, 1:22 PM.
Tags
None
Referenced Files
F17947693: D10944.id.diff
Thu, Jul 31, 6:00 PM
F17926457: D10944.diff
Wed, Jul 30, 1:09 PM
Unknown Object (File)
Jun 7 2025, 12:58 AM
Unknown Object (File)
Jun 1 2025, 2:35 AM
Unknown Object (File)
May 21 2025, 12:32 PM
Unknown Object (File)
May 9 2025, 3:02 AM
Unknown Object (File)
May 8 2025, 11:05 PM
Unknown Object (File)
Apr 29 2025, 5:33 PM
Subscribers

Details

Summary

Ref T6238. On the instance management interface, I want to check if an instance's database is reachable by connecting to it.

If it isn't, we hang for 30-60 seconds (default connection timeout). Allow explicit specification of a timeout when establishing a connection instead.

This only does MySQLi, not MySQL. We don't need MySQL for now, although it would be nice to support it eventually (Ref T6710).

Test Plan
  • Browsed around.
  • Used short timeouts to get instance database status in instance management.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Support an explicit connection timeout parameter for database connections.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Dec 8 2014, 5:11 PM
This revision was automatically updated to reflect the committed changes.