Why does my cluster not show the correct numeric resource attribute?

When a new host joins the cluster

This behavior occurs if the newly joined host has the numeric resource attribute configured in the local ego.conf file, and a default value of the same numeric attribute is defined in the cluster configuration file (ego.cluster.cluster_name). The customized value in the local ego.conf is not updated until the primary LIM is restarted.

To fix this issue, log on to the primary host in the cluster and use the following command to restart the primary LIM:

egosh ego restart

When the value is changed on an existing host

If the cluster does not reflect the updated numeric resource attribute after the value is changed on the host, remove the host from the cluster and rejoin it to the cluster, so that the updated value in the local ego.conf file can take effect.
  1. To remove the host from the cluster:
    1. Shut down EGO on the host:

      egosh ego shutdown

    2. Remove the host from the cluster:

      egosh resource remove host_name

  2. After changes are made to the local ego.conf, start EGO on the host to make the host rejoin the cluster:

    egosh ego start

Note: If a default value of the same numeric attribute is defined in the cluster configuration file, you may also need to restart the primary LIM after the host rejoins the cluster. See the preceding FAQ in this topic.