# Ray data read\_text calls read all of input hogging memory and spilling **URL:** \ **Category:** Ray Data\ **Created:** [June 17, 2025, 8:03am UTC](https://discuss.ray.io/t/ray-data-read-text-calls-read-all-of-input-hogging-memory-and-spilling/22667 "2025-06-17T08:03:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![vgill](https://avatars.discourse-cdn.com/v4/letter/v/a88e4f/32.png) [@vgill](https://discuss.ray.io/u/vgill)\ **Post date:** [June 17, 2025, 8:03am UTC](https://discuss.ray.io/t/ray-data-read-text-calls-read-all-of-input-hogging-memory-and-spilling/22667/1 "2025-06-17T08:03:39Z")
**1. Severity of the issue: (select one)** None: I’m just curious or want clarification. Low: Annoying but doesn’t hinder my work. Medium: Significantly affects my productivity but can find a workaround. [X] High: Completely blocks me. **2. Environment:** - Ray version: 2.36 - Python version: 3.9 - OS: AL2023 - Cloud/Infrastructure: AWS - Other libs/tools (if relevant): **3. What happened vs. what you expected:** - Expected: Ray data read\_text gets backpressure from following slower stages, slows down and does not materialize the whole dataset. - Actual: Ray data read\_text read all of data without waiting for the subsequent stages to consume it, all of the data gets spilled and then Ray SpillWorker hogs a huge chunk of memory for ever, even when all of the code that created the ray data pipeline goes out of scope. ---
**Author:** ![christina](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/christina/32/7542_2.png) [@christina](https://discuss.ray.io/u/christina)\ **Post date:** [June 17, 2025, 11:05pm UTC](https://discuss.ray.io/t/ray-data-read-text-calls-read-all-of-input-hogging-memory-and-spilling/22667/2 "2025-06-17T23:05:11Z")
What errors specifically seeing from the Ray Spillworker, is it out of memory error? Do you have any logs we can take a look at?