-
Notifications
You must be signed in to change notification settings - Fork 476
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
network: new default gossip fanout setting for relays #5005
network: new default gossip fanout setting for relays #5005
Conversation
…ssip fanout when nodes are configured as relays.
Codecov Report
@@ Coverage Diff @@
## master #5005 +/- ##
==========================================
+ Coverage 53.63% 53.65% +0.01%
==========================================
Files 432 432
Lines 54057 54059 +2
==========================================
+ Hits 28996 29004 +8
+ Misses 22812 22811 -1
+ Partials 2249 2244 -5
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
…ding to codegen/expose into local_defaults.go
|
||
// If gossip fanout has not been explicitly overridden, use defaultRelayGossipFanout | ||
// rather then the default gossip fanout setting from defaultLocal | ||
if source.GossipFanout == defaultLocal.GossipFanout { |
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.
does this prevent relays from explicitly overriding this fanout change back the current local default value of 4?
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.
Yes, though they could set 3 or 5.
This should go with #5018 |
Summary
Introduce override of default gossip fanout to a new default relay gossip fanout when nodes are configured as relays.
Test Plan
Configured node with netAddress and ran locally with and without gossipFanout overridden.