Skip to content

Add pool max fails logic #422

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

Closed
KaymeKaydex opened this issue Dec 24, 2024 · 2 comments
Closed

Add pool max fails logic #422

KaymeKaydex opened this issue Dec 24, 2024 · 2 comments
Labels
needs feedback Something is unclear with the issue

Comments

@KaymeKaydex
Copy link

it is necessary to give and write the logic of behavior in case of unavailability of one of the nodes, I suggest using a similar approach with nginx and the max_fails setting in upstream

https://nginx.org/en/docs/stream/ngx_stream_upstream_module.html#upstream

@oleg-jukovec
Copy link
Collaborator

oleg-jukovec commented Dec 27, 2024

I think we can not give such a guarantee due to an asynchronous nature of the connector: you could push N requests to a connection and only than get an error.

@oleg-jukovec oleg-jukovec added the needs feedback Something is unclear with the issue label Dec 27, 2024
@KaymeKaydex
Copy link
Author

Yes, we discussed this idea and decided that it is enough on client side

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
needs feedback Something is unclear with the issue
Projects
None yet
Development

No branches or pull requests

2 participants