none
Activity timeout fail before defined timeout

    Question

  • Hi, 

    I have this copy activity moving data from Azure Data Lake Store to Azure SQL DB which is embedded inside a foreach activity that iterates runs from a pipeline. Overall, this means 96 copies running of around 22000 rows each (and there are previous activities too within the same pipeline)

    In order to avoid timeouts I left the timeout of the activities set at default (which is 7 days). On friday (8th June) I left the pipeline running, but the next day I found that one of the copy activities had failed (after running little more than 2 hours) with the error message:

    • ''Type=System.Data.SqlClient.SqlException,Message=Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.,Source=.Net SqlClient Data Provider,SqlErrorNumber=-2,Class=11,ErrorCode=-2146232060,State=0,Errors=[{Class=11,Number=-2,State=0,Message=Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.,},],''

    I would like to know why is this happening and what can I do to avoid it. 

    Thank you, 

    Monday, June 11, 2018 10:01 AM

Answers

  • Yes you are right, I didn't realise before, thanks. Just in case anyone has the same problem, I ended up modifying the dependency settings to make the copies dependent on each other (so that they don't happen in parallel and collapse the ASQLDB). 
    Monday, June 11, 2018 12:31 PM

All replies

  • This is not expired due to copy activity timeout. It seems that your query timeout. You could refer to  this link.
    Monday, June 11, 2018 12:03 PM
  • Yes you are right, I didn't realise before, thanks. Just in case anyone has the same problem, I ended up modifying the dependency settings to make the copies dependent on each other (so that they don't happen in parallel and collapse the ASQLDB). 
    Monday, June 11, 2018 12:31 PM