Metabase 0.50.x high CPU and OOM crashes after upgrading from 0.49
Shows how to fix metabase 0.50.x high CPU and OOM crashes after upgrading from 0.49. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Upgrade to Metabase 0.50.7 or newer. The thread leak fix shipped in PR #45253 in the 0.50.7+ releases; the maintainers asked everyone on the thread to upgrade to 0.50.7 and then closed the issue once the fix was out.
Steps
- - Downgrading back to 0.49.12 (made the symptoms go away).
MB_SQL_PARSING_ENABLED=false(helped some setups but not the OOMs).
- The durable fix is the patched release, not a config flag.
When to use
You are seeing this: After upgrading Metabase from 0.49.x to 0.50.x, many deployments saw severe CPU spikes and memory growth, with containers crashing every few hours from out-of-memory. Use this skill when you run into "Metabase 0.50.x high CPU and OOM crashes after upgrading from 0.49".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: 0.49.12, Metabase 0.50.7. If you are on something much newer or older, the details may have shifted.
Why this happens
This was a real regression in the 0.50 line, not a config problem.