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

Remove the old peer discovery mechanism since v2 is default #1816

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

thampiotr
Copy link
Contributor

@thampiotr thampiotr commented Oct 3, 2024

PR Description

Now that we had run this code for a while, we're happy to remove the old v1 cluster peer discovery mechanism since the v2 works without issues as a drop-in replacement.

Which issue(s) this PR fixes

Fixes #1274

Notes to the Reviewer

PR Checklist

  • CHANGELOG.md updated
  • Documentation added
  • Tests updated
  • Config converters updated

@thampiotr thampiotr marked this pull request as ready for review October 3, 2024 13:05
@thampiotr thampiotr requested a review from a team as a code owner October 3, 2024 13:05
@mattdurham
Copy link
Collaborator

Does this change the behavior any of join peers or the discovery string? Taking a quick look it doesnt appear to but want to double check.

@thampiotr
Copy link
Contributor Author

Does this change the behavior any of join peers or the discovery string? Taking a quick look it doesnt appear to but want to double check.

No, because it was default from the time we merged it. We had a way to switch back to the old discovery, and this is what we're removing here.

There is also one feature that was enabled only for experimental users, but we tested it sufficiently too, so it's becoming the default.

@mattdurham
Copy link
Collaborator

mattdurham commented Oct 3, 2024

Did how used to handle buildJoinAddresses change? Looks like the v1 handled it differently on looking up the SRV address. IE if I was using v1 discovery and using it as a DNS lookup does that still work?

@mattdurham
Copy link
Collaborator

It looks like it should work through the SRVResolver but its enough different I am unsure.

Copy link
Collaborator

@mattdurham mattdurham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thampiotr thampiotr changed the title Make new cluster peer discovery default Remove the old peer discovery mechanism since v2 is default Oct 3, 2024
@thampiotr thampiotr force-pushed the thampiotr/remove-old-peer-discovery-code branch from b9a2e9e to af36368 Compare October 3, 2024 13:51
@thampiotr
Copy link
Contributor Author

It looks like it should work through the SRVResolver but its enough different I am unsure.

Sorry for the confusion. As discussed offline - we currently use v2 by default and we had a flag that allowed to switch back to v1 in case of issues. Since v2 works fine, I'm removing the flag and deleting the v1. There are no changes required by users, this is fully compatible with old configs.

@thampiotr thampiotr merged commit 0a650fc into main Oct 3, 2024
18 checks passed
@thampiotr thampiotr deleted the thampiotr/remove-old-peer-discovery-code branch October 3, 2024 14:53
@clayton-cornell clayton-cornell added the type/docs Docs Squad label across all Grafana Labs repos label Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/docs Docs Squad label across all Grafana Labs repos
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Graduate the improvements to clustering to GA once proven
3 participants