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.

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

[Feature] Fallback/backup node #424

Open
pkesso opened this issue Apr 15, 2024 · 0 comments
Open

[Feature] Fallback/backup node #424

pkesso opened this issue Apr 15, 2024 · 0 comments

Comments

@pkesso
Copy link

pkesso commented Apr 15, 2024

I use chproxy for SELECT distribution. I have a single-node 'cluster' in chproxy config for this, however, when the designated node is not ok, I would like to pass requests to another node, which should not be used, when primary is available.

I woud like to have a 'backup' of 'fallback' node in cluster settings, similar to backup upstream in NGINX - the node to send traffic if primary is not available.

Node weight would be fine too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant