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.-
Community SupportThanks 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.
Community SupportJust 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 !!