Avoiding timeouts during DocType updates. | Umbraco | Page 1

proper quail Sep 6, 2023, 1:00 PM

#

How does one go about avoiding a timeout during a document type update?

I have a DocType I'm trying to update, but it will always timeout, no matter what kind of update I am trying to make. The database is hosted on Azure, but it's a normal SQL Instance, I am not using Umbraco Cloud.

At first I was convinced this was due to some Azure configuration as this never used to happen prior to the migration to Azure, and my local development instance (SQL Server Express) accepts the changes just fine.

However, I've since been given a copy of the production database, restored locally (not connecting through Azure) and I get the same timeout errors.

Pulled from the logs, I get a few repeats of this error:

System.Data.SqlClient.SqlException (0x80131904): Lock request time out period exceeded.\r\nThe statement has been terminated.\r\n

followed by:

System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

How can I go about correcting this? It's a massive sticking point right now.

proper quail Sep 6, 2023, 4:09 PM

#

Is there perhaps a way I can hook into some Umbraco events so I can see exactly how far the update gets before timing out?

Anything to help me debug and remedy this issue. I cannot imagine a couple of hundred content nodes being a problem?

fallow shore Sep 6, 2023, 8:22 PM

#

v8 used to have Umbraco.Core.SqlWriteLockTimeOut which you defaulted to 5 secs and could be extended to 20secs ?

looks like it changed name in v10
https://docs.umbraco.com/umbraco-cms/reference/configuration/globalsettings#distributed-write-lock-defaulttimeout

Globalsetting SqlWriteLockTimeOut has been removed
This setting has been superseded by DistributedLockingWriteLockDefaultTimeout````

might help?

#Avoiding timeouts during DocType updates.