Forum Discussion

zakeer1517's avatar
zakeer1517
Regular Visitor
1 year ago
Solved

InvalidHttpRequestToLivy: from cannot be less than 0 HTTP status code: 400

We are currently integrating data from the bronze to silver layer using a DAG that runs notebooks in parallel with a concurrency level of 5. However, the process consistently fails after approximatel...
Data Engineering
  • zakeer1517's avatar
    zakeer1517
    1 year ago

    Hi v-kpoloju-msft 

     

    I haven't opened any support ticket. I was able to fix the issue by increasing the concurrency limit to 20 by which the execution time falls with in the session time out limit (28-29 mins). 

     

    Thanks for the support. 

     

     

v-kpoloju-msft's avatar
v-kpoloju-msft
Community Support
1 year ago

Hi zakeer1517,

Thanks for the follow up question. As I mentioned in my previous post, please consider raising a support ticket. This will allow the engineering team to investigate the backend Livy logs and session handling in detail.

Thank you for using the Microsoft Community Forum.

  • v-kpoloju-msft's avatar
    v-kpoloju-msft
    Community Support
    1 year ago

    Hi zakeer1517,

    We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

    If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

    Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

     

    Thank you for your understanding and participation.

    • zakeer1517's avatar
      zakeer1517
      Regular Visitor
      1 year ago

      Hi v-kpoloju-msft 

       

      I haven't opened any support ticket. I was able to fix the issue by increasing the concurrency limit to 20 by which the execution time falls with in the session time out limit (28-29 mins). 

       

      Thanks for the support. 

       

       

      • v-kpoloju-msft's avatar
        v-kpoloju-msft
        Community Support
        1 year ago

        Hi zakeer1517,

        Thank you for the update, and I’m glad to hear that increasing the concurrency limit resolved the issue and helped keep the execution time within the session timeout window.

        Appreciate you sharing the solution, it may help others facing a similar challenge. If you run into any further questions or need assistance in the future, feel free to reach out.

        Please give us 'Kudos' and mark your post as the accepted solution so other members can find it more easily.

        Thank you for using the Microsoft Community Forum.