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.
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
Support neighsyncd system warmreboot. #661
Support neighsyncd system warmreboot. #661
Changes from all commits
35604a4
07eb5ac
debc1fc
5960c7c
742ac62
922ed14
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Just some thought on current restore_neighbors.py implementation. For system warm reboot, the stale entries won't be filtered out and has to wait for a new cycle of arp age out time interval, then the whole reconciliation logic in neighsyncd becomes redundant (skippable). neighorch simply drops the duplicate entries and accept new entries.
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.
It is not exactly true, in case the neighbor ports were down during the warm reboot, the neighbor entries won't be inserted to kernel so we need reconciliation logic to remove them.
Also it is good to use the same logic/code path to handle both scenarios.
On top of that, we are still exploring the solutions to only get alive entries into kernel during the restoring phase if possible in later PRs.
So overall, we should use the same reconciliation logic.