-
Notifications
You must be signed in to change notification settings - Fork 52
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
Support polling specific Vitess cells #124
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't really comment on the go lang, but at a high level this change seems fine. Should bring vitess behavior into parity with non-vitess ways of checking health. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense on the vitess side of things. Also, hello!
Thanks for the review @shlomi-noach 👋 |
@shlomi-noach / @drogart / @tomkrouper: can anyone foresee a need for a single Freno leader to poll more than one Vitess cell? If so I might make the new config field |
I think the answer lies within your specific deployment layout. Will you always have a |
Agreed, thanks @shlomi-noach! For our use case there will probably always be 1 x Freno leader per Vitess cell, but I suppose making the setting more flexible now is better than later I'll update this PR to accept an array/slice of cells to poll in case this is useful for someone 👍 |
This PR adds support for polling MySQL replicas from a specific Vitess "cell"
This change is backwards compatible with the current logic that fetches replicas from any Vitess cell. This change resolves duplicated Freno probing when Freno is deployed with a share domain and many Vitess cells