Read only, front-end server is attempting to delete entry from cmsContentXml
We are using a load balancer in our test environment. We have configured Umbraco using this, this, and this.
Our environment looks like the diagram above but instead of all servers hitting the same database, each server has its own db. Our master server writes to a master database. Then, on a database level, these changes are propagated out to all other databases which are explicitly read-only.
After configuring everything like the documentation recommends, we had no issues creating new content or editing existing content. But after deleting a content node, we have an issue were a front-end server tries to delete an entry from cmsContentXml. This is not necessary as the master server already does this and the changes are propagated out. The front-end server cache (memory) remains out of date until the entire site is republished.
As long as content editors republish the entire site after any deletions, there doesn't seem to be any immediate issues. But the error is still thrown which is worrisome. Is there any way to stop absolutely all db writes from a front-end server?
Read only, front-end server is attempting to delete entry from cmsContentXml
We are using a load balancer in our test environment. We have configured Umbraco using this, this, and this.
Our environment looks like the diagram above but instead of all servers hitting the same database, each server has its own db. Our master server writes to a master database. Then, on a database level, these changes are propagated out to all other databases which are explicitly read-only.
After configuring everything like the documentation recommends, we had no issues creating new content or editing existing content. But after deleting a content node, we have an issue were a front-end server tries to delete an entry from cmsContentXml. This is not necessary as the master server already does this and the changes are propagated out. The front-end server cache (memory) remains out of date until the entire site is republished.
As long as content editors republish the entire site after any deletions, there doesn't seem to be any immediate issues. But the error is still thrown which is worrisome. Is there any way to stop absolutely all db writes from a front-end server?
We are using Umbraco 7.4.3
The relevant log entry
is working on a reply...