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

Allow disabling shotover peers check #1773

Merged
merged 1 commit into from
Oct 15, 2024

Conversation

rukai
Copy link
Member

@rukai rukai commented Oct 15, 2024

This PR makes the check_shotover_peers_delay_ms field optional.
When it is not provided the shotover peers check task is not started meaning that shotover nodes are always considered up and no TCP connections are created against shotover peers.

I think this field should be mandatory, we should force users to configure shotover to route around down shotover nodes, however, for now, lets make it optional to make it an easier transition.

@rukai rukai force-pushed the make_shotover_peers_check_optional branch from 9e99bca to 1a651a6 Compare October 15, 2024 00:40
Copy link

codspeed-hq bot commented Oct 15, 2024

CodSpeed Performance Report

Merging #1773 will not alter performance

Comparing rukai:make_shotover_peers_check_optional (d0aaa6c) with main (5a41409)

Summary

✅ 39 untouched benchmarks

@justinweng-instaclustr
Copy link
Collaborator

Should transforms.md be updated as well to mention check_shotover_peers_delay_ms is optional?

@rukai rukai force-pushed the make_shotover_peers_check_optional branch from 1a651a6 to fbd7ba4 Compare October 15, 2024 01:36
@rukai
Copy link
Member Author

rukai commented Oct 15, 2024

yeah thats a good idea, done.

@rukai rukai force-pushed the make_shotover_peers_check_optional branch from fbd7ba4 to d0aaa6c Compare October 15, 2024 01:37
@rukai rukai merged commit a3cef2c into shotover:main Oct 15, 2024
41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants