Control hosts (Windows)

You can start, stop, and restart local, remote, and multiple Windows hosts. Find information on each of these options.

Start hosts

Starting hosts brings them into the cluster where they become usable resources.

Start a local Windows host

Log on as egoadmin.

To start a local host, perform the following steps:

  1. Start an interactive command console.
  2. Start EGO on your local host.

    egosh ego start

Start a remote Windows host

Log on as egoadmin. If the master host is up, log onto any host in the cluster; if the master is down, log onto a management host.

Start EGO on your remote host:

egosh ego start host_name

Replace host_name with the name of your remote host.

Start multiple Windows hosts

Log on as egoadmin. If the master host is up, log onto any host in the cluster; if the master is down, log onto a management host.

Start EGO on multiple hosts:

egosh ego start host_name host_name ...

Replace host_name with the names of your remote hosts. Separate host names with a space.

Shut down hosts

Shutting down a host immediately changes the host state to Unavailable. Running workload is automatically restarted on another host. If you need to perform maintenance, you can choose to close a host instead of shutting it down.

Removing a management host requires following a separate procedure.

Stop a local Windows host

Log on as egoadmin.

Stop EGO on your local host:

egosh ego shutdown

Stop a remote Windows host

Log on as egoadmin. If the master host is up, log onto any host in the cluster; if the master is down, log onto a management host.

Stop EGO on your remote host:

egosh ego shutdown host_name

Replace host_name with the name of your remote host.

Stop multiple Windows hosts

Log on as egoadmin. If the master host is up, log onto any host in the cluster; if the master is down, log onto a management host.

Stop EGO on more than one host:

egosh ego shutdown host_name host_name ...

Replace host_name with the names of your remote hosts. Separate host names with a space.

Enable automatic expiry of unavailable compute hosts

By default, all hosts that join the cluster remain in the cluster, even if they become unusable.

Optionally, after a period of time in the Unavailable state, a compute host can expire from the cluster—it no longer appears in the Console, or in egosh resource list or resource view output, and it is not affected by egosh start all or restart all commands.

Host expiry is not irreversible. If you restart an expired host (for example, run egosh ego start host_name or restart the host while automatic system startup is configured), it can rejoin the cluster in the same way that a newly installed host joins the cluster.

If you want to remove a management host from the cluster, a different procedure is required.

To configure the host expiry feature, take the following steps.

  1. Logon as egoadmin and edit ego.conf.
  2. Specify a time-out period for the parameter EGO_DYNAMIC_HOST_TIMEOUT.

    The default time period is in hours. Use an M after the time value to represent minutes (for time periods of 10 minutes or more).

    For example:

    • EGO_DYNAMIC_HOST_TIMEOUT=48 means the unavailable host is removed after 48 hours.

    • EGO_DYNAMIC_HOST_TIMEOUT=75M means the host is removed after an hour and fifteen minutes.

    • EGO_DYNAMIC_HOST_TIMEOUT=2M means the host is removed after 10 minutes; a value of 2 minutes is below the allowable 10 minute minimum.

  3. Restart the master host for the change to take effect.

Remove management hosts from the cluster

You must have previously enabled automatic expiry of unavailable compute hosts.

Hosts that have been added to a cluster using the egoconfig mghost cmd and are designated as management hosts need to be physically deleted from ego.cluster.cluster_name if you want to remove them from the cluster. This requirement applies to current management hosts.

  1. Shut down the host.
  2. If you have configured automatic startup during your cluster setup, then run egoremoverc.sh.

    Doing this prevents automatic startup when the host reboots, which keeps the host from being re-added dynamically to the cluster.

  3. If the host is a master candidate, run egoconfig masterlist to remove the host from the failover order.
  4. Run egoconfig unsetmghost to remove the host from the management host group.

    Running this command removes the host entry from ego.cluster.cluster_name.

  5. Run the installer (MSI file) on the host you wish to remove from the cluster, and uninstall the EGO package.
  6. Restart the master host to change it from a management host to a compute host.

    Because the host is shut down, and daemons are no longer running, the host switches to an unavailable state. Now that you’ve got a compute host in an unavailable state, complete the steps for enable automatic expiry of unavailable compute hosts to remove the host from the cluster.

Restart hosts

You may want to restart a host if it has become unavailable to the cluster. An unavailable host may have problems with memory or unnecessary applications that can be fixed by restarting it.

Restart a local Windows host

Log on as egoadmin.

Restart EGO on your local host:

egosh ego restart

Restart a remote Windows host

Log on as egoadmin. If the master host is up, log onto any host in the cluster; if the master is down, log onto a management host.

Restart EGO on your remote host:

egosh ego restart host_name

Replace host_name with the name of your remote host.

Restart multiple Windows hosts

Log on as egoadmin. If the master host is up, log onto any host in the cluster; if the master is down, log onto a management host.

Restart EGO on multiple hosts:

egosh ego restart host_name host_name ...

Replace host_name with the names of your remote hosts. Separate host names with a space.