Significant System CPU usage increase maybe caused by MongoDB Automation Agent release

Our System CPU usage approximately doubled this morning and I’m trying to figure out why. I have looked into the logs and noticed that the times when it went up roughly correspond to a change in the version number for the MongoDB Automation Agent.

I haven’t been able to find any change in query patterns that would explain such a large jump in CPU usage, and our Process CPU usage remained relatively flat.

I’m wondering if anyone else has noticed this and if there’s anything I can do about it.

1 Like

We have had the same scenario on both of our clusters. The jump corresponded with the Automation Agent update as well. One of our clusters is a DEV clusters with minimal DB activity, so we felt it had to be a result of the Automation Agent update.

In our case it also caused some Atlas alerts for high CPU usage.

Same here, with no code or usage change, our cluster’s system CPU went from ~20% to ~40%.

Bumping this thread. This issue is still ongoing and the extra CPU usage is keeping one of our clusters in a higher tier than it should be (which is costing us money). Hopefully a MongoDB employee can see this and chime in.

Same here, it caused our cluster to auto-scale to the next level tier…

I got confirmation from mongodb support today that the issue has been resolved and that it was indeed related to the automation agent.

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.