This issue occurs when the Edge VM is placed and running on an overcommitted ESXi host.
Edge is resource sensitive. If the Edge is deployed on a ESXi host which does not have dedicated resources for the Edge VM, and if the resources are overcommitted, the Edge starts experiencing:
To recover from the issue: