This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
Hi everyone,
I'm running a notebook in Microsoft Fabric where I read a large file, around 2GB.
The notebook takes a long time to execute, and eventually I receive the following error:
InvalidHttpRequestToLivy: Session -------- of workspace --------- on pool -------- is not running. It is either completed or not fully yet ready. Scheduler state : Scheduled. Plugin state : Cleanup. Livy state : dead HTTP status code: 400. Trace ID: --------.
My question is: Can this issue be handled from the code side, or is it more likely related to Spark/Livy configuration settings? What would be the best way to fix it?
Has anyone experienced something similar when processing large files in Fabric?
Any guidance would be greatly appreciated.
Thanks in advance!
Solved! Go to Solution.
Hello @gbetancurm
It is probably a driver out-of-memory issue, which would happen if you're using Pandas dataframe instead of Spark. Pandas is not distributed by design, so none of the executors are used and the driver gets overloaded.
You can start by looking at the Spark application details > Logs > Driver - you should find additional details on why the application failed.
Hi @gbetancurm ,
We wanted to kindly follow up regarding your query. If you need any further assistance, please reach out.
Thank you.
Hi @gbetancurm ,
Thanks for reaching out to Microsoft Fabric Community.
Just checking in to see if the response provided by @deborshi_nag was helpful.
If you have reviewed the Spark application Driver logs as suggested and still need further assistance, please feel free to share additional details so we can assist further.
Thank you.
Same error here, but in synapse analytics.
Hello @gbetancurm
It is probably a driver out-of-memory issue, which would happen if you're using Pandas dataframe instead of Spark. Pandas is not distributed by design, so none of the executors are used and the driver gets overloaded.
You can start by looking at the Spark application details > Logs > Driver - you should find additional details on why the application failed.
Check out the June 2026 Fabric update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.