We've been running with Umbraco 7.6.3 on a live multi-site load balanced installation since late 2017 without issue. We recently upgraded to Umbraco 7.10.4.
Part of the website uses the UmbracoHelper.TypedMediaAtRoot() in order to retrieve a series of media nodes. Since upgrading to Umbraco 7.10.4 this query is no longer returning any data in our production environment.
The following message is within the logs:
2018-05-08 11:28:05,506 [P4648/D9/T34] WARN Umbraco.Web.PublishedCache.XmlPublishedCache.PublishedMediaCache - Failed (10 times) to retrieve medias from Examine index and had to load them from DB. This may indicate that the Examine index is corrupted.
Rebuilding the internal Examine indexes (or any others) from within the CMS back-office does not fix the issue.
Using the MediaService to retrieve media directly from the database works correctly and the expected media are returned. However as you'd expect, the performance is worse.
In addition we have been logging approximately a total of 40 System.Data.SqlClient.SqlException exceptions being throw daily by the following calls:
System.Data.SqlClient.SqlException: Transaction (Process ID 84) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
I've increased the logging to verbosity to ALL, but I haven't been able to spot any extra clues.
My thoughts are that the upgrade process did not work correctly or that there are bugs present in 7.10.4 that are causing these issues.
Has anyone else experienced something similar or have any suggestions to moving forwards?
Upgrade to 7.10.4 causing UmbracoHelper.TypedMediaAtRoot() failures and SqlException deadlocks
We've been running with Umbraco 7.6.3 on a live multi-site load balanced installation since late 2017 without issue. We recently upgraded to Umbraco 7.10.4.
Part of the website uses the UmbracoHelper.TypedMediaAtRoot() in order to retrieve a series of media nodes. Since upgrading to Umbraco 7.10.4 this query is no longer returning any data in our production environment.
The following message is within the logs:
Rebuilding the internal Examine indexes (or any others) from within the CMS back-office does not fix the issue.
Using the MediaService to retrieve media directly from the database works correctly and the expected media are returned. However as you'd expect, the performance is worse.
In addition we have been logging approximately a total of 40 System.Data.SqlClient.SqlException exceptions being throw daily by the following calls:
These are logging exceptions with the message
I've increased the logging to verbosity to ALL, but I haven't been able to spot any extra clues.
My thoughts are that the upgrade process did not work correctly or that there are bugs present in 7.10.4 that are causing these issues.
Has anyone else experienced something similar or have any suggestions to moving forwards?
Thanks Peter
is working on a reply...