Cap. 14. Status - Aici sunt dragoni

Cuprins

Most users never need to understand the contents of the status section and can be happy with the output from crm_mon.

However for those with a curious inclination, this section attempts to provide an overview of its contents.

14.1. Node Status

In addition to the cluster’s configuration, the CIB holds an up-to-date representation of each cluster node in the status section.

Exemplu 14.1. O intrare iniţială de status pentru un nod sănătos numit cl-virt-1

  <node_state id="cl-virt-1" uname="cl-virt-2" ha="active" in_ccm="true" crmd="online" join="member" expected="member" crm-debug-origin="do_update_resource">
   <transient_attributes id="cl-virt-1"/>
   <lrm id="cl-virt-1"/>
  </node_state>

Users are highly recommended not to modify any part of a node’s state directly. The cluster will periodically regenerate the entire section from authoritative sources. So any changes should be done with the tools for those subsystems.

Tabel 14.1. Surse Autoritative pentru Informaţia de Stare

Dataset	Sursă Autoritativă
`node_state fields`	crmd
`transient_attributes tag`	attrd
`lrm tag`	lrmd

The fields used in the node_state objects are named as they are largely for historical reasons and are rooted in Pacemaker’s origins as the Heartbeat resource manager.

They have remained unchanged to preserve compatibility with older versions.

Tabel 14.2. Câmpuri de Status ale Nodului

Câmp	Descriere
`id`	Unique identifier for the node. Corosync based clusters use the uname of the machine, Heartbeat clusters use a human-readable (but annoying) UUID.
`uname`	The node’s machine name (output from `uname -n`).
`ha`	Flag specifying whether the cluster software is active on the node. Allowed values: `active`, `dead`.
`in_ccm`	Flag for cluster membership; allowed values: `true`, `false`.
`crmd`	Flag: is the crmd process active on the node? One of `online`, `offline`.
`join`	Flag saying whether the node participates in hosting resources. Possible values: `down`, `pending`, `member`, `banned`.
`expected`	Expected value for `join`.
`crm-debug-origin`	Diagnostic indicator: the origin of the most recent change(s).

Clusterul foloseşte aceste câmpuri ca să determine dacă, la nivel de nod, nodul este sănătos sau este într-o stare defectuoasă şi trebuie evacuat forțat.