Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The timeout config for pool init does not work #47

Open
Winging opened this issue Aug 17, 2021 · 2 comments
Open

The timeout config for pool init does not work #47

Winging opened this issue Aug 17, 2021 · 2 comments
Labels
community Source: who proposed the issue good first issue Good for newcomers type/enhancement Type: make the code neat or more efficient

Comments

@Winging
Copy link
Contributor

Winging commented Aug 17, 2021

It seems that the timeout config for pool init does not work, the connetion initialization got hang there if the address is not correct? Any ideas about this?
@Shylock-Hg
Copy link
Contributor

The timeout in configuration means request timeout not connection timeout.
So don't use the incorrect address.

@Winging
Copy link
Contributor Author

Winging commented Aug 21, 2021

The timeout in configuration means request timeout not connection timeout.
So don't use the incorrect address.

I think it's necessary to have such a timeout configuration for connection. So that user would know he has a incorrect address or port

@jamieliu1023 jamieliu1023 mentioned this issue Aug 21, 2021
Closed
@Sophie-Xie Sophie-Xie added type/enhancement Type: make the code neat or more efficient community Source: who proposed the issue labels Sep 28, 2021
@Sophie-Xie Sophie-Xie added the good first issue Good for newcomers label Nov 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
community Source: who proposed the issue good first issue Good for newcomers type/enhancement Type: make the code neat or more efficient
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Winging @Shylock-Hg @Sophie-Xie