You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue occurs whenever we are transferring the schema for a table from schema_x_staging to schema_x and concurrently run an insert statement (or probably any DML operation) against a table in schema_x. The transfer and insert statements end up stuck in Running and Suspended state, respectively. As per the link you send, the transfer statement locks the whole schema, resulting in a deadlock whenever an insert is ran against any other table in the schema. To make matters worse, Synapse doesn't seem to detect/resolve deadlocks properly: https://dba.stackexchange.com/questions/300929/how-are-deadlocks-detected-by-synapse
dlt version
0.4.8
Describe the problem
This issue occurs whenever we are transferring the schema for a table from
schema_x_staging
toschema_x
and concurrently run an insert statement (or probably any DML operation) against a table inschema_x
. The transfer and insert statements end up stuck inRunning
andSuspended
state, respectively. As per the link you send, the transfer statement locks the whole schema, resulting in a deadlock whenever an insert is ran against any other table in the schema. To make matters worse, Synapse doesn't seem to detect/resolve deadlocks properly: https://dba.stackexchange.com/questions/300929/how-are-deadlocks-detected-by-synapseFull discussion: https://dlthub-community.slack.com/archives/C06EYJ2Q37C/p1712571682549229
Expected behavior
No response
Steps to reproduce
Operating system
Windows
Runtime environment
Local
Python version
3.8
dlt data source
No response
dlt destination
No response
Other deployment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: