Hi Simon,

The scheduler was configured on both servers I guess. Best to enable the scheduler only on one instance in the load balanced setup.

Just remove the cmsimportscheduler module from web.config.

Hope this helps,

Richard

The web.config is sync'd between servers which unfortunately means this is not an option. It needs to be sync'd to ensure the config is identical on all servers behind the load balancer.

Hmm then there is no real solution I'm affraid. You could cancel each the importing events on the servers that are not allowed to run the import but that is not an ideal solution. Is it for the same import you need the proxy on? Maybe only allow one server to access that proxy?

Yes it's the same site. I'm wondering if it is possible to use the new load balancing features to check that the server is the master and not a slave and prevent them being run on slave servers?

Just having a quick poke around in the Core and they appear to check like this:

switch (_appContext.GetCurrentServerRole())
{
    case ServerRole.Slave:
        LogHelper.Debug<ScheduledTasks>("Does not run on slave servers.");
        return true; // DO repeat, server role can change
    case ServerRole.Unknown:
        LogHelper.Debug<ScheduledTasks>("Does not run on servers with unknown role.");
        return true; // DO repeat, server role can change
}

// ensure we do not run if not main domain, but do NOT lock it
if (_appContext.MainDom.IsMainDom == false)
{
    LogHelper.Debug<ScheduledTasks>("Does not run if not MainDom.");
    return false; // do NOT repeat, going down
}

Yeah would be possible if CMSImport only supported those versions but it's also supported on V6 and that is an issue since it needs to work on that version also.

OK, I will have a think about how we can get around this in a backwards compatible way :)

Was thinking about the recordimporting events but will have a look if I can add a cancel option to those other events as well. But a workaround for your problem might be to throw an exception in importing event maybe?

Hmm, just ran into the same issue here on a load-balanced, replicated environment. It appears that, when manually executed, the CMS Import process is being restarted after a random number of items is imported. Have you thought out anything in the meantime Richard? Or has anyone found a solid workaround?

Not yet, but the events simon describes should work. Or you need to make sure CMSImport can only be called from a single server.

Best,

Richard

Here is what I implemented in my class that inherits from ApplicationEventHandler:

void CmsImport_RecordImporting(object sender, CMSImport.Extensions.Providers.ImportProviders.EventArgs.RecordImportingEventArgs e)
{
    // Get the current server role using the new features added in 7.2.4
    var serverRole = UmbracoContext.Current.Application.Services.ServerRegistrationService.GetCurrentServerRole();

    if (serverRole != ServerRole.Single && serverRole != ServerRole.Master)
    {
        e.Cancel = true;
        global::Umbraco.Core.Logging.LogHelper.Info<EventHandlers>("CMS Import Record Import Cancelled As Calling Server is not Master");
    }
}

Excellent, I will implement that.

How is determined that the CurrentServerRole is ServerRole.Master? Is there a switch I need to set somewhere? Our hosting company setup the load balanced environment, so I want to verify it's setup correctly.

There is a table in the database where all servers are registered umbracoServer. Servers in your load balanced setup will be registered in this table when they are discovered by Umbraco.

You can manually set the master server if you wish - see Explicit Master Scheduling server

There is loads of really useful information on the Flexible Load Balancing setup.

Try the example above from Simon. That would work..

is working on a reply...