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
F14017877: D10944.diff
Tue, Nov 5, 12:21 AM
F13986624: D10944.id.diff
Mon, Oct 21, 4:21 AM
F13974903: D10944.id26285.diff
Fri, Oct 18, 7:52 AM
Unknown Object (File)
Mon, Oct 7, 1:18 AM
Unknown Object (File)
Sep 17 2024, 7:35 AM
Unknown Object (File)
Sep 12 2024, 6:32 AM
Unknown Object (File)
Sep 5 2024, 10:32 AM
Unknown Object (File)
Sep 4 2024, 7:55 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.