We noticed that our machines running the self hosted integration runtime all started experiencing high CPU on Sunday morning (14th March 2021) ~ 7am GMT.
There was no ADF pipeline activity occurring at that time.
Closer analysis revealed that the SHIR updater was the culprit and we stopped the windows service 'Integration Runtime Updater'. This immediately brought the CPU down.
In the RCA, we discovered the machine hosting the integration runtime, windows event viewer shows errors about unable to access a registry key (image attached)
Is this a known issue? There have been no problems with the SHIR or ADF, just this updater service.
Additional Notes :
"Integration Runtime Service" Properties > Log On > Correctly configured to run as account DIAHostService as per docs (this must have been done by the installer)
"Integration Runtime Update Service" Properties > Log On > "Local System account" is checked. Is this the problem?