This project is read-only.

Issue with web farms

Topics: Administration, Core, General, Installing Orchard
Aug 17, 2012 at 7:00 PM

So I'm probably noticing this more and more because of my frustrating work trying to get a second level cache working for Azure, but there are definitely ... anomalies with Orchard.

All of the following is assuming running on Azure web farm with 2 instances.

Like when enabling a module. Often I need to enable it twice.

Sometimes when editing a type shortly after creating it I get a message that the type doesn't exist



Is this something that I should be worried about? Is it something that I should *not* worry about due to the changes to NH?

Thoughts/experiences welcome :)

Aug 17, 2012 at 7:20 PM

You should not worry about it. You are not supposed to edit the content types and install module on this kind of environment. You don't want to do it in production directly. Editing content though is what you want to do in prod.

There is an open issue for this, which is to plug the internal cache manager to a common source, like you are doing right now for NH, but low priority.