Forum Discussion
Livy HTTP Request Error
Thanks for sharing the update. Since the job succeeds when run under a different account, the issue seems tied to resource load or background operations in the original dev account rather than Livy itself. Switching accounts works as a workaround, but it’s not the only option.
A better long-term approach would be to:
-
Reviewing Fabric capacity metrics to check if background jobs are consuming resources.
-
Coordinating with your admin to isolate heavy Spark workloads onto a dedicated capacity or workspace.
-
Adjusting background activity in the dev account to reduce contention.
Hope it helps !!
Thank You.-
I tried everything, but nothing worked until I switched the account I was using to run the notebook. A colleague advised me to switch accounts because in the dev account I was using there were a lot of background operations and he thought it might work if I used another account specifically to run these kinds of notebooks. As soon as I changed the account, the notebook ran without any errors. But is this the only way? What if the notebook fails after a month? Do I have to switch accounts then too?
v-aatheequeCommunity Support
Thanks for sharing the update. Since the job succeeds when run under a different account, the issue seems tied to resource load or background operations in the original dev account rather than Livy itself. Switching accounts works as a workaround, but it’s not the only option.
A better long-term approach would be to:
-
Reviewing Fabric capacity metrics to check if background jobs are consuming resources.
-
Coordinating with your admin to isolate heavy Spark workloads onto a dedicated capacity or workspace.
-
Adjusting background activity in the dev account to reduce contention.
Hope it helps !!
Thank You.- v-aatheeque
Just checking Were you able to review the Fabric capacity metrics or coordinate with your admin to check if background Spark workloads were causing the issue in your dev account?
Since switching accounts worked as a workaround, it would be good to confirm if the long-term steps helped resolve the contention problem.
looking forward for your response !!
-