QoS queue counters reporting negative values after config reload. #679
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.
The counter cache file is not removed while config reload but COUNTER_DB gets cleaned up.·
This was resulting in counters in COUNTER_DB lesser than that in cache file resulting into -ve counter display.
Signed-off-by: Prasanth Kunjum Veettil prasanth.kunjumveettil@broadcom.com
- What I did
Fix for QoS counters reporting negative values after config reload
- How I did it
The counter cache file is not removed while config reload but COUNTER_DB gets cleaned up.·
This was resulting in counters in COUNTER_DB lesser than that in cache file resulting into -ve counter display.
- How to verify it
Start traffic
show queue counter
config reload
wait for the system to come up.
show queue counter
- Previous command output (if the output of a command-line utility has changed)
- New command output (if the output of a command-line utility has changed)
-->