You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like POA coordinates the installation of the patches using update domain but it download the updates at the same time across all nodes. In theory, this process should be (?) light weight but this last patch caused CPU to spike up on all of the nodes in every region.
Based on POA logs, the initial spike that happened on all nodes corresponds to the time POA started to download the update. After that, you can see CPU spikes in phases probably due to POA actually installing the patches update domain by domain.
I don't know why the CPU spiked during the downloading phase (maybe the system was scanning or updates or malware?). Regardless of the cause, this could bring the entire system down if something bad happens say consumed all of the CPUs.
To avoid this from happening, should download of the patches also happen in phases?
The text was updated successfully, but these errors were encountered:
It seems like POA coordinates the installation of the patches using update domain but it download the updates at the same time across all nodes. In theory, this process should be (?) light weight but this last patch caused CPU to spike up on all of the nodes in every region.
Based on POA logs, the initial spike that happened on all nodes corresponds to the time POA started to download the update. After that, you can see CPU spikes in phases probably due to POA actually installing the patches update domain by domain.
I don't know why the CPU spiked during the downloading phase (maybe the system was scanning or updates or malware?). Regardless of the cause, this could bring the entire system down if something bad happens say consumed all of the CPUs.
To avoid this from happening, should download of the patches also happen in phases?
The text was updated successfully, but these errors were encountered: