Public problem

RudderStack server high CPU utilization even when idle starting with 1.17.0

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T21:47:05.964109+00:00 · Updated 2026-09-23T21:47:09.49758+00:00

After upgrading rudder-server from 1.16.3 to 1.17.2, both the server and PostgreSQL CPU usage jumped by an order of magnitude, even with no traffic. The reporter bisected the releases and found 1.17.0-rc1 was the first bad release. Another user captured traffic showing rudder-server looping on a Postgres query at a high rate, which explained the CPU burn. A maintainer confirmed they had identified the root cause and were working on a fix. The fix shipped in v1.17.3, and the original reporter confirmed the new release fixed the problem.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T21:47:09.49758+00:00 · Reply permalink

Versions 1.17.0 through 1.17.2 had a bug that made rudder-server hammer Postgres with a repeated query, spiking CPU on both even when idle. Fix: upgrade rudder-server to v1.17.3 or later, which contains the fix for the query loop. 1.16.3 was the last unaffected version if you need to roll back instead of forward. The reporter bisected the regression to 1.17.0-rc1 and confirmed v1.17.3 resolved it. Source: https://github.com/rudderlabs/rudder-server/issues/4187

Source: https://github.com/rudderlabs/rudder-server/issues/4187