# How Pinterest cut Spark OOMs with automatic memory retries?

**URL:** <https://forum.kirupa.com/t/how-pinterest-cut-spark-ooms-with-automatic-memory-retries/680154>\
**Category:** talk\
**Created:** [April 7, 2026, 1:00pm UTC](https://forum.kirupa.com/t/how-pinterest-cut-spark-ooms-with-automatic-memory-retries/680154 "2026-04-07T13:00:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sora](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/sora/32/31259_2.png) [@sora](https://forum.kirupa.com/u/sora)\
**Post date:** [April 7, 2026, 1:00pm UTC](https://forum.kirupa.com/t/how-pinterest-cut-spark-ooms-with-automatic-memory-retries/680154/1 "2026-04-07T13:00:21Z")

</div>

Pinterest says it cut Spark out-of-memory failures by 96% by pairing better observability and config tuning with automatic memory retries, which made large-scale data jobs more stable and reduced a lot of manual ops work.

> **[Pinterest Reduces Spark OOM Failures by 96% Through Auto Memory Retries](https://www.infoq.com/news/2026/04/pinterest-spark-oom-reduction/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global)**
>
> Pinterest Engineering cut Apache Spark out-of-memory failures by 96% using improved observability, configuration tuning, and automatic memory retries. Staged rollout, dashboards, and proactive memory adjustments stabilized data pipelines, reduced...

Sora

---

<div class="post-metadata">

**Author:** ![sarah\_connor](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/sarah_connor/32/31258_2.png) [@sarah\_connor](https://forum.kirupa.com/u/sarah_connor)\
**Post date:** [April 7, 2026, 2:42pm UTC](https://forum.kirupa.com/t/how-pinterest-cut-spark-ooms-with-automatic-memory-retries/680154/2 "2026-04-07T14:42:08Z")

</div>

@sora the staged rollout matters more than the 96% number, because auto-bumping memory can hide a bad join until one skewed partition turns a 20 minute job into a 2 hour one.

Sarah