You observe that a Regional Hub is unstable and continually restarts or flaps approximately every 20-30 minutes. During these episodes, the Hub probe lags in processing the queued data from associated robots. Eventually, the hub status alternates between green and red in Infrastructure Manager. The logs show that the controller probe is restarting the hub probe due to non-response to the controller requests.
While a definitive root cause is not fully determined, the instability is linked to a high volume of persistent connections on Hub port 48001. A specific robot machine is creating dozens of established connections that do not close immediately, eventually overwhelming the Hub's ability to process QoS data and causing the probe to stop responding the the controller probe. When the controller doesn't receive a response, it restarts the hub probe..
You can stabilize the Hub by identifying the problematic robot and tuning the Hub's session handling parameters.