Disable the feature that decreases link probe interval for measuring switch overhead #49
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
vdahiya12
approved these changes
Mar 31, 2022
… DISABLE_decreaseLinkProberIntervalAfterSwitchover
4 tasks
zjswhhh
added a commit
that referenced
this pull request
Apr 1, 2022
…switch overhead #49 (#54) ### Description of PR Can't cleanly cherry pick the commit from master branch: 34a68d1 disable switchover measuring based on link prober (#49) Summary: Fixes # (issue) Disable part of the feature introduced in #43. The link probing interval will NOT be decreased by default. Link prober state change events will still be posted in `LINK_PROBE_STATS|PORTNAME` in state db. sign-off: Jing Zhang [email protected] ### Type of change - [x] New feature ### Approach #### What is the motivation for this PR? We need to reconsider the design of this feature. To be more specific, this is a special case of decreasing probing interval, it's for measurement purposes only. We still want to trigger the toggle in 300ms when pack loss happens. The negative count should be 30 instead of 3 when interval is decreased to 10ms.
|
This commit could not be cleanly cherry-picked to 202012. Please submit another PR. |
|
PR submitted and merged already. |
6 tasks
zjswhhh
added a commit
to zjswhhh/sonic-linkmgrd
that referenced
this pull request
Apr 15, 2022
…switch overhead sonic-net#49 (sonic-net#54) ### Description of PR Can't cleanly cherry pick the commit from master branch: 34a68d1 disable switchover measuring based on link prober (sonic-net#49) Summary: Fixes # (issue) Disable part of the feature introduced in sonic-net#43. The link probing interval will NOT be decreased by default. Link prober state change events will still be posted in `LINK_PROBE_STATS|PORTNAME` in state db. sign-off: Jing Zhang [email protected] ### Type of change - [x] New feature ### Approach #### What is the motivation for this PR? We need to reconsider the design of this feature. To be more specific, this is a special case of decreasing probing interval, it's for measurement purposes only. We still want to trigger the toggle in 300ms when pack loss happens. The negative count should be 30 instead of 3 when interval is decreased to 10ms.
zjswhhh
added a commit
to sonic-net/sonic-buildimage
that referenced
this pull request
Apr 17, 2022
[master][sonic-linkmgrd] submodule updates 41f5fb9 Jing Zhang Mon Apr 11 08:33:39 2022 -0700 Upgrade linkmgrd to `BULLSEYE` (sonic-net/sonic-linkmgrd#60) 2fc890e Jing Zhang Mon Apr 4 10:25:22 2022 -0700 Lower unsolicited MUX state change notification log level to WARNING (sonic-net/sonic-linkmgrd#57) 13f4879 Jing Zhang Sun Apr 3 21:56:33 2022 -0700 Keep incrementing sequence number when link prober is suspended and shutdown (sonic-net/sonic-linkmgrd#55) 62482e1 Jing Zhang Sun Apr 3 20:54:40 2022 -0700 Reset link prober state when default route is back (sonic-net/sonic-linkmgrd#56) 34a68d1 Jing Zhang Thu Mar 31 18:33:46 2022 -0700 disable switchover measuring based on link prober (sonic-net/sonic-linkmgrd#49) 898a655 Jing Zhang Thu Mar 31 15:42:15 2022 -0700 Update link prober metrics posting logics (sonic-net/sonic-linkmgrd#50) sign-off: Jing Zhang [email protected]
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 of PR
Summary:
Fixes # (issue)
Disable part of the feature introduced in #43.
The link probing interval will NOT be decreased by default. Link prober state change events will still be posted in
LINK_PROBE_STATS|PORTNAMEin state db.sign-off: Jing Zhang [email protected]
Type of change
Approach
What is the motivation for this PR?
We need to reconsider the design of this feature.
To be more specific, this is a special case of decreasing probing interval, it's for measurement purposes only. We still want to trigger the toggle in 300ms when pack loss happens. The negative count should be 30 instead of 3 when interval is decreased to 10ms.
How did you do it?
How did you verify/test it?
Any platform specific information?
Documentation