pool: add GetInstances method, that returns current instances connections state #428
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KaymeKaydex
force-pushed
the
get-instances
branch
from
bb4d014 to
2d6df0d
Compare
…ions state The GetConnections method has been added, which is necessary to monitor the current state of the pool. This should help implement dynamic tracking of tarantool topology changes.
KaymeKaydex
force-pushed
the
get-instances
branch
from
2d6df0d to
bb0aea7
Compare
|
We already have similar method: https://pkg.go.dev/github.com/tarantool/go-tarantool/[email protected]/pool#ConnectionPool.GetInfo |
|
closed cause #429 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The GetConnections method has been added, which is necessary to monitor the current state of the pool. This should help implement dynamic tracking of tarantool topology changes.
What has been done? Why? What problem is being solved?
I didn't forget about (remove if it is not applicable):
Related issues: