Why are tasks running on my master host?

When a cluster is not configured for failover, by default tasks can execute on any resource group (assuming that the default configuration for resReq and ResourceGroupName is used in Consumer section of the application profile).

When a cluster is configured for failover, by default work only runs on hosts that are not configured to be management hosts (hosts that are not marked with the mg resource attribute). Work does not run on any CPU slot in the ManagementHosts resource group.

For performance or other reasons you may not want workload to run on the master host. It is possible to change your configuration to dedicate the master host as a management host. In this way, you ensure no application workload runs on your master host.

Prevent tasks from running on your master host by configuring failover

You configure failover with the command egoconfig mghost shared_top. Running this command on the master host sets the shared directory for the cluster, copies configuration files to the shared directory, adds the host to the ManagementHosts resource group, and configures the mg resource attribute for the host.

Prevent tasks from running on your master host by manually changing the configuration

Log on to the host as the cluster administrator. For example, egoadmin.

If you do not want to configure failover for any reason, you can follow these steps to manually prevent tasks from running on your master host.

  1. Open the cluster file on the master host for editing.

    Linux/UNIX—$EGO_CONFDIR/ego.cluster.cluster_name

    Windows—%EGO_CONFDIR%\ego.cluster.cluster_name

  2. Find the Host section.
    Begin Host
    ...
    End Host
  3. Locate your master host name and in the RESOURCES column add the mg resource attribute for your master host.

    This designates your master host as a management host only. Application workload will not run on this host.

    For example:

    Begin Host
    HOSTNAME  model    type        r1m  mem  swp  RESOURCES    #Keywords
    ...
    host1    !        NTX86       -   -    -    (nt mg)
    ...
    End Host
  4. Save the file.
  5. Restart EGO on the master host.

    egosh ego restart host1