Our team commonly works with a shared database during development for all local instances (local1, local2, local3, etc) as well as a continuous integration environment (dev.client.domain.com) . This has worked fine for us up until 7.3.
Now, with the new load balancing behavior in 7.3+ described here http://issues.umbraco.org/issue/U4-6992, this is causing our schedule tasks to fail as depending on the order of events, any one of the various instances could be considered "Master" - so the dev.client instance is then considered a slave and won't run the scheduled tasks.
How can we turn this "auto master/slave" logic off so the scheduled jobs on dev.client.domain.com will run regardless of any other instances pointing to the same database?
Umbraco 7.3.1 with Shared Database
Our team commonly works with a shared database during development for all local instances (local1, local2, local3, etc) as well as a continuous integration environment (dev.client.domain.com) . This has worked fine for us up until 7.3.
Now, with the new load balancing behavior in 7.3+ described here http://issues.umbraco.org/issue/U4-6992, this is causing our schedule tasks to fail as depending on the order of events, any one of the various instances could be considered "Master" - so the dev.client instance is then considered a slave and won't run the scheduled tasks.
How can we turn this "auto master/slave" logic off so the scheduled jobs on dev.client.domain.com will run regardless of any other instances pointing to the same database?
is working on a reply...