-
Notifications
You must be signed in to change notification settings - Fork 887
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
merge ringpop services #5080
merge ringpop services #5080
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.
I think the submodule changes are unintentional?
And need to rebase on top of main?
common/membership/ringpop/monitor.go
Outdated
|
||
rpo.initialized.Set(struct{}{}, nil) | ||
} | ||
|
||
// bootstrap ring pop service by discovering the bootstrap hosts and joining the ring pop cluster | ||
func (rpo *monitor) bootstrapRingPop( | ||
bootstrapHostPostRetriever func() ([]string, error), |
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.
this can be simplified more.. just call rpo.fetchCurrentBootstrapHostports
directly and use healthyHostLastHeartbeatCutoff/2
for the backoff interval
Yeah probably, damnit. I have too much going on with this repo |
I was lazy when I merged these
Whoops
d874c60
to
6a40b71
Compare
@@ -1,6 +1,4 @@ | |||
version: v1beta1 | |||
deps: | |||
- buf.build/googleapis/googleapis |
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.
🙁 I think I needed to add this to get proto generation to work correctly on a branch
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.
That's weird: it broke suddenly in CI for me :/
What changed?
I merged the ringpop
service
with the membership monitor.Why?
It's not a useful abstraction
How did you test it?
Potential risks
Is hotfix candidate?
No.