bgpd: Prevent unnecessary re-install of routes#19788
Merged
riw777 merged 1 commit intoFRRouting:masterfrom Oct 21, 2025
Merged
Conversation
There is this sequence of events that is happening: a) BGP registers for a nexthop resolution for address A b) <time passes and BGP comes fully up> c) Something else in the system requests for the same nexthop resolution tracking for A d) Zebra wakes up and decides to send a update to BGP about the nexthop, even when nothing has happened. e) BGP decides that the nexthop has not changed but goes ahead and reinstalls everything again anyways. Let's modify BGP to be a bit smarter here. It already knows that the nexthop hasn't changed, there is no need to run bgp_process on each route that is using the BNC. Let's stop this from happening. This is only 1/2 the fix. I want to protect BGP from zebra but I also want zebra to not send the update to BGP in this case. That change is going to come in a different set of commits because it's a bit larger of a problem and will need a bit more work. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Member
Author
|
@Mergifyio backport stable/10.4 stable/10.5 |
✅ Backports have been createdDetails
|
This was referenced Jan 20, 2026
Jafaral
added a commit
that referenced
this pull request
Jan 21, 2026
bgpd: Prevent unnecessary re-install of routes (backport #19788)
ton31337
added a commit
that referenced
this pull request
Jan 21, 2026
bgpd: Prevent unnecessary re-install of routes (backport #19788)
17 tasks
This file contains hidden or 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
3 participants
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.
There is this sequence of events that is happening:
a) BGP registers for a nexthop resolution for address A b)
c) Something else in the system requests for the same nexthop resolution tracking for A
d) Zebra wakes up and decides to send a update to BGP about the nexthop, even when nothing has happened. e) BGP decides that the nexthop has not changed but goes ahead and reinstalls everything again anyways.
Let's modify BGP to be a bit smarter here. It already knows that the nexthop hasn't changed, there is no need to run bgp_process on each route that is using the BNC. Let's stop this from happening.
This is only 1/2 the fix. I want to protect BGP from zebra but I also want zebra to not send the update to BGP in this case. That change is going to come in a different set of commits because it's a bit larger of a problem and will need a bit more work.