# Ray data \`ReadParquet-\>SplitBlocks(2)\` shows failure even though the entire ray job is successful

**URL:** <https://discuss.ray.io/t/ray-data-readparquet-splitblocks-2-shows-failure-even-though-the-entire-ray-job-is-successful/22567>\
**Category:** Ray Data\
**Created:** [May 28, 2025, 7:48am UTC](https://discuss.ray.io/t/ray-data-readparquet-splitblocks-2-shows-failure-even-though-the-entire-ray-job-is-successful/22567 "2025-05-28T07:48:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![brian-tang](https://avatars.discourse-cdn.com/v4/letter/b/a698b9/32.png) [@brian-tang](https://discuss.ray.io/u/brian-tang)\
**Post date:** [May 28, 2025, 7:48am UTC](https://discuss.ray.io/t/ray-data-readparquet-splitblocks-2-shows-failure-even-though-the-entire-ray-job-is-successful/22567/1 "2025-05-28T07:48:49Z")

</div>

Medium: Significantly affects my productivity but can find a workaround.

**2. Environment:**

- Ray version: 2.41.0
- Python version: 3.11
- OS: AL2
- Cloud/Infrastructure: AWS EKS 1.30
- Other libs/tools (if relevant):

**3. What happened vs. what you expected:**

- Expected: `ReadParquet->SplitBlocks(2)` should not show errors when the whole Ray job is successful
- Actual: `ReadParquet->SplitBlocks(2)` shows errors even though the output is correct and expected and Ray job was successful

Hi all,

We’ve been using Ray for sometime, but only recently started dipping our toes in ray data. I ran a very simple Ray application to test ray.data but when I inspect the logs in our Ray cluster, I’m seeing a failure here with `ReadParquet->SplitBlocks(2)`, albeit the overall Ray job is shown as successful:

 ![Screenshot 2025-05-28 at 3.41.00 PM](https://us1.discourse-cdn.com/flex020/uploads/ray/original/2X/0/03c7b7eb54e78e6a65e37629022977e35e2e021c.png)

This job was executed on an existing Ray cluster with one available ray worker with sufficient memory, with ray autoscaler enabled.

I then scaled up a few more additional workers first before running the job, and there weren’t anymore failures. Oddly, I printed out the row counts of the ray dataset and file sizes for in both cases (the job that had the failed `ReadParquet->SplitBlocks(2)`, and without), and they both tally up.

So my question is, is this error something expected, and should not need to worry about since the overall job succeeded? Even if so, what’s the cause of `ReadParquet->SplitBlocks(2)` error?

---

<div class="post-metadata">

**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 3, 2025, 11:22pm UTC](https://discuss.ray.io/t/ray-data-readparquet-splitblocks-2-shows-failure-even-though-the-entire-ray-job-is-successful/22567/2 "2025-06-03T23:22:52Z")

</div>

Hello! I believe this is due to an autoscaling error, this is mentioned a bit here. [Debugging Ray Data auto-scaling errors | Anyscale Docs](https://docs.anyscale.com/monitoring/debugging-ray-data-auto-scaling/)

So yes, you don’t need to worry about the errors since the overall job succeeded. The error is from the cluster not having enough resources to satisfy the splitting blocks requirement. If you experience a lot of these errors though, this might mean your cluster needs more resources allocated to them, so you might want to adjust your autoscaling or resource allocation for those jobs.