-
Notifications
You must be signed in to change notification settings - Fork 60
go-tarantool/v2/pool.Add: no logs on single connection failure #389
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Thank you for the feedback! This doesn't look like a priority bug or issue, so I can't promise we'll start working on it soon. But you could create a pull request with We have some ideas to improve logging for |
Alright, i`ll try to do a request with logs in described parts today. Backlog state looks good. |
Add err log to ConnectionPool.Add() in case, when unable to establish connection and ctx is not canceled; also added logs for error case of ConnectionPool.tryConnect() calls in ConnectionPool.controller() and ConnectionPool.reconnect() Part of tarantool#389
Add err log to ConnectionPool.Add() in case, when unable to establish connection and ctx is not canceled; also added logs for error case of ConnectionPool.tryConnect() calls in ConnectionPool.controller() and ConnectionPool.reconnect() Part of #389
Create pool with empty set of instances:
Later, try to add new instances via add method:
When unable to establish connection with tarantool, i got no err here, no message in logs.
First of all, no any logging at pool/connection_pool.go:285, if
canceled
variable is false.Second - no any err handling and logging at pool/connection_pool.go:1419.
Easy proposal: add some basic
log.Printf
for logging errors in code above.Hard proposal:
This can allow:
The text was updated successfully, but these errors were encountered: