@Ethan-TP : When the controller starts up completely, Its CPU usage is low (5%). It tuns nornally at 5-10% CPU if their are no managment plane interactions. IF we interact using mobile app, web app, etc with the controller, its CPU usage momentarilty shoots up to 100% and within a few seconds falls back to the nor,al (5-10%) level. It runs like this for days, weeks and even months, if left undisturbed.

However if their are heavy ineractions from mangement plane, at some instant the CPU usage becomes 100% and does not come down to the normal level even if left alone for hours. Obsviously at this time problems happen in network, web UI and mobile app become unresponsive, wifi traffic falls (means its main function impacted) and we have to restart this controller to restre the network health. THis is what I mean by infinite dead loop. I also noticed when this event of dead loop happens, the mongo DB usage has also preaked abnormally (from the 400MB+ we see mongo db using it shoots up to ~650 MB)


The logs are uploaded and shared here:

https://drive.google.com/drive/folders/1S2hxhueh2bWZo_TbIyzsuY2hW3cnTCSr?usp=sharing