PublishedContentHandler Import Fail: Failed to acquire write lock for id: -333
Hi,
We have a Umbraco 10.4.x solution hosted in Azure Web Apps which has two front end web servers, both with multiple instances, and an admin server (single instance). We configured correctly following this guide:
We sometimes get this error when trying to publish using usync Complete Publisher from staging to production. Not much online about it other than to refresh the database cache. But that's not a great solution for our clients if it happens regularly.
Any thoughts on what could be causing or any solutions you know of out there?
I haven't come across this one before, so not loads to add at the moment. However I think its deep in Examine indexing and last time i looked at anything like that on azure and load balancing i got lost in the world of. "Temp" vs "Synced" Directory factories, so i don't know if there is something worth looking into around that ?
I have a vauge recollection that front end servers would have one setting and the backend another ? but i don't have enough examine nouse to really say what would be what
Thanks for that - yes I think that the direction to be looking in as well but thought I'd run it by you see you had any come across it before, its unlikely to be specifically publisher related but that does actually help us to pin down the cause so appreciate that. I think we need to do some advanced setup so the servers know their roles etc.... should be a fun fix lol.
PublishedContentHandler Import Fail: Failed to acquire write lock for id: -333
Hi,
We have a Umbraco 10.4.x solution hosted in Azure Web Apps which has two front end web servers, both with multiple instances, and an admin server (single instance). We configured correctly following this guide:
https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/load-balancing/azure-web-apps
We sometimes get this error when trying to publish using usync Complete Publisher from staging to production. Not much online about it other than to refresh the database cache. But that's not a great solution for our clients if it happens regularly.
Any thoughts on what could be causing or any solutions you know of out there?
Thanks,
Hi Mike,
I haven't come across this one before, so not loads to add at the moment. However I think its deep in Examine indexing and last time i looked at anything like that on azure and load balancing i got lost in the world of. "Temp" vs "Synced" Directory factories, so i don't know if there is something worth looking into around that ?
https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/load-balancing/file-system-replication#examine-directory-factory-options
I have a vauge recollection that front end servers would have one setting and the backend another ? but i don't have enough examine nouse to really say what would be what
https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/load-balancing/azure-web-apps#lucene-examine-configuration
HI Kevin,
Thanks for that - yes I think that the direction to be looking in as well but thought I'd run it by you see you had any come across it before, its unlikely to be specifically publisher related but that does actually help us to pin down the cause so appreciate that. I think we need to do some advanced setup so the servers know their roles etc.... should be a fun fix lol.
Cheers,
Mike
is working on a reply...