Router config: set peers_failover_brokering
to false
#341
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Zenoh, the
routing.router.peers_failover_brokering
configuration is by default set totrue
.This setting makes a router to route the messages between 2 peers, until it detects (via gossip scouting) that they are directly inter-connected with each other. For other use cases than ROS, it makes sense to have this configuration enabled by default in case some peers cannot establish direct connections.
But in ROS default configuration, all Nodes are running on the same host and will establish direct connections with each other. If some Nodes are running on a distinct hosts, they could:
Thus, for ROS having
peers_failover_brokering: true
serves no purpose and has some drawbacks related to the additional management overhead by the router and extra messages during the Nodes startup.