Weird\poor performance with Copy Activity

[daniele_tiles]

Hi,

we've tried to make a simple Copy Activity from one of our SQL Server to a Lakehouse. 

It's only 6 table, and the biggest is about 680k rows (not even millions).

So the first run went great, it was fast. After that, the second and subsequent runs aren't performing at all.

The 5 small tables are completed, while the biggest is always in a running state. 0 rows copied, we check with Azure Data Studio while it's running. In our last run of today it's been running for almost 1 hour and half.

Any idea of what could be the issue? The Copy Activity is in overwrite.

[daniele_tiles]

We also tried to delete the Lakehouse, and start from scratch. But the issue is the same.

[Anonymous]

Hi @daniele_tiles ,

Best way to troubleshoot this is by reaching our support team.

Please go ahead and raise a support ticket to reach our support team: Link 

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Thank you.

[Anonymous]

Hello @daniele_tiles ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to create a support ticket.

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Thank you.

[Anonymous]

Hi @daniele_tiles ,

Apologies for the issue you have been facing. I would like to check are you still facing this issue? 

It's difficult to tell what could be the reason for this performance. I would request you to wait for sometime or stop the pipeline and do a re-try.

If the issue still persists, please reach out to our support team so they can do a more thorough investigation on why this it is happening: Link 

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Hope this helps. Please let us know if you have any other queries.

[daniele_tiles]

Hi @Anonymous ,

it just failed with the following error:

"Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Lakehouse operation failed for: The stream was already consumed. It cannot be read again"

Really strange. Any idea?

[daniele_tiles]

Hi,

yes we're still facing the issue. We've got here the execution history:

The first time it ran correctly in about 2 minutes. but adter that it's been hanging for hours.