-
Notifications
You must be signed in to change notification settings - Fork 156
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
Add intelligence to xcvrd to understand process restart and config reload #356
Comments
Also, need to discuss and understand multi-ASIC behavior/handling in these new use-cases |
Based on technical discussion between CSCO-MSFT team, plan is to go with option#3 out of three options brainstormed First option, files/image_config/misc/docker-wait-any can be used to build dependency b/w dockers, for eg- syncd/swss docker restart can trigger pmon docker restart, but this is not desirable, since pmon has other platform processes, we are primarily interested in restarting xcvrd. [NO-GO] Second option, below APIs are invoked during swss restart, needs investigation if this could be leveraged to trigger xcvrd restart. [NO-GO] Third option (chosen one, updated previous proposal): #356 [AI-Mihir] |
Updated proposal based on 6/12 CSCO-MSFT discussion to cover multi-NPU platforms:
|
I just have another thought: why not fix the issue from portsorch.cpp side? Here is my proposal: In portsorch.cpp, we shall cache all the serdes attributes. We shall compare the cached serdes attributes values with incoming values while doPortTask is called. If the value equals, no need apply the value to SAI. Any comment? @prgeor @mihirpat1 @jaganbal-a |
Please don't use SIGKILL. SIGTERM is more appropriate, just in case there is platform specific cleanup that needs to done. |
Upon xcvrd/pmon docker restart set the media settings in app DB which sends spurious SI programming from OA upon receiving. xcvrd should not set the settings upon process restart/pmon restart.
So add intelligence to xcvrd to understand the process restart and config reload.
-Create a new table "TABLE_xcvrd" by xcvrd to set a magic number and process restart count in STATE_DB upon fresh start. (config reload/cold reboot)
-Upon xcvrd process restart /pmon docker restart, xcvrd to check the magic number presence on coming up path to understand whether it is a restart case or a fresh start case.
-Mask spurious notification during process restart
The text was updated successfully, but these errors were encountered: