FE; monitor BIRD route statistics #460
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Monitor BIRD route statistics.
BGP functionality in FE also accepts non-default routes, but a huge set of routing entries could have a negative effect on the system (e.g., increased memory usage).
As part of connectivity monitoring, print number of routes hosted by the default BIRD routing tables (master4/master6), and log memory usage. (Routing stats are polled every second.)
Note: BIRD seems to block route related queries via the CLI during reconfiguration and during processing routes.
Based on some basic tests on Kind:
100.000 IPv4 routes increases BIRD's memory consumption by 10MB.
Announcing the same set of routes via a second gateway (multipath routing) adds roughly 50-60%.
Pushing 2*100.000 IPv4 routes from one remote BGP peer (running BIRD) took a bit more than 2 seconds.
Issue link
#453
Checklist