-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[active-standby] Fix default route handler race condition (#254)
What is the motivation for this PR? Fix the race condition of the default route notification. This is similar to #104 If there are multiple default route notifications received by linkmgrd, the mux port posts the default route handlers wrapped by strand. But boost asio doesn't guarantee the execution order of the default route handlers, so the final state machine default route could be any intermediate default route state. For example, for default route notifications like: [2024-06-20 08:28:57.872911] [warning] MuxPort.cpp:365 handleDefaultRouteState: port: EtherTest01, state db default route state: na [2024-06-20 08:28:57.872954] [warning] MuxPort.cpp:365 handleDefaultRouteState: port: EtherTest01, state db default route state: ok The final state machine default route state could be "ok" if the handler for "ok" is executed after the handler for "na". The final state machine default route state could be "na" if the handler for "ok" is executed before the handler for "na". Signed-off-by: Longxiang Lyu [email protected] Work item tracking Microsoft ADO (number only): 28471183 How did you do it? post the default route handlers directly through strand instead of using strand::wrap, so the handlers are executed in the same order as the handlers' post order. How did you verify/test it? without this PR, UT fail: Signed-off-by: Longxiang Lyu <[email protected]>
- Loading branch information
1 parent
5730b79
commit 26dbdc7
Showing
4 changed files
with
51 additions
and
3 deletions.
There are no files selected for viewing
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
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
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
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