Skip to content

Unify connection_acquisition_timeout behavior #1215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: 6.x
Choose a base branch
from

Conversation

robsdedude
Copy link
Member

The config option connection_acquisition_timeout now spans anything that's required to acquire a working connection from the pool. This includes

  • Potentially fetching a routing table This entails acquiring a connection in itself.
  • Bolt, TLS, TCP handshaking
  • Authentication
  • Any other required IO (e.g., DNS lookups)
  • Waiting for room in the pool
  • possibly more

Previously, the timeout wold be restarted for auxiliary connection acquisitions like those for fetching a routing table.

The config option `connection_acquisition_timeout` now spans anything that's
required to acquire a working connection from the pool. This includes
 * Potentially fetching a routing table
   This entails acquiring a connection in itself.
 * Bolt, TLS, TCP handshaking
 * Authentication
 * Any other required IO (e.g., DNS lookups)
 * Waiting for room in the pool
 * possibly more

Previously, the timeout wold be restarted for auxiliary connection acquisitions
like those for fetching a routing table.
@robsdedude robsdedude force-pushed the unify-connection-acquisition-timeout branch from 963a6ec to 58600d6 Compare June 27, 2025 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant