-
Notifications
You must be signed in to change notification settings - Fork 273
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
Fixing race condition for rif counters #1136 (202205 branch) #1202
Conversation
@prsunny , @Junchao-Mellanox , @kcudnik , @dgsudharsan Please note that the cherry pick in 202205 branch failed for (#1136) , so this PR was needed. All the details are mentioned in this PR. |
@sumanbrcm can you help look into the test failure? |
54bf9e7
to
090a376
Compare
Changes for 202205 branch Signed-off-by: Suman Kumar <[email protected]>
090a376
to
979b623
Compare
/azpw run Azure.sonic-sairedis |
/AzurePipelines run Azure.sonic-sairedis |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Commenter does not have sufficient privileges for PR 1202 in repo sonic-net/sonic-sairedis |
/azpw run Azure.sonic-sairedis |
/AzurePipelines run Azure.sonic-sairedis |
Azure Pipelines successfully started running 1 pipeline(s). |
Changes for 202205 branch
sairedis: Fixing race condition for rif counters #1136
swss: Fixing race condition for rif counters sonic-swss#2488
Unit Tests:-
The steps followed are same as in sonic-net/sonic-buildimage#11621
After RIF creation derived info of oid for RIF from "COUNTERS_RIF_NAME_MAP"
127) "Vlan100"
128) "oid:0x6000000000aa5"
Checked all the tabled in COUNTER_DB which has same OID in keys
127.0.0.1:6379[2]> keys 6000000000aa5
127.0.0.1:6379[2]>
Deleted the RIF by removing the ip on the intf.
Checked COUNTER_DB again with same OID if there are stale entries or not. No stale entries exist now.
127.0.0.1:6379[2]> keys 6000000000aa5
(empty array)
127.0.0.1:6379[2]>
Signed-off-by: Suman Kumar [email protected]