Cisco Bug: CSCvv84616 - CPS | Mongo:v3.4.16 | Worthlessness of DB lock percentage values in bulkstats and Grafana
Sep 25, 2020
- Cisco Policy Suite for Mobile
Known Affected Releases
Symptom: In this example, we are using West Sac SESSION SET, SESSION:set06a PRIMARY - wspcrfsm03 When checking lock percentage into bulkstats numero is "0.0" cat bulk-wspcrfoam01-202009231920.csv | grep "set06a" G,wspcrfsm03,set06a.lock.percent,0.0 G,wspcrfsm03,set06a.wspcrfsm03_27717_lock.percent,0.0 G,wspcrfsm04,set06a.wspcrfsm04_27717_lock.percent,0.0 On session sets, the values for inserts and updates is reasonably high, in the dozens to over a 100. I thought surely this would have at least some lock percentages, like 5% or so. To see a database with writes have no lock percentage is weird. Conditions: Our mongo release at TMO is 3.4.16 When checking percentages across all nodes wee see all nodes are in "0%" Found out by typing: find -name bulk* -mmin -5 | xargs grep _lock.percentage | awk -F, '($NF > 0)'
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases