12.2. Transient Node Attributes

Like regular node attributes, the name/value pairs listed here also help describe the node. However they are forgotten by the cluster when the node goes offline. This can be useful, for instance, when you only want a node to be in standby mode (not able to run resources) until the next reboot.

In addition to any values the administrator sets, the cluster will also store information about failed resources here.


     <transient_attributes id="cl-virt-1">
      <instance_attributes id="status-cl-virt-1">
       <nvpair id="status-cl-virt-1-pingd" name="pingd" value="3"/>
       <nvpair id="status-cl-virt-1-probe_complete" name="probe_complete" value="true"/>
       <nvpair id="status-cl-virt-1-fail-count-pingd:0" name="fail-count-pingd:0" value="1"/>
       <nvpair id="status-cl-virt-1-last-failure-pingd:0" name="last-failure-pingd:0" value="1239009742"/>
      </instance_attributes>
     </transient_attributes>

Figure 12.2. Example set of transient node attributes for node "cl-virt-1"

In the above example, we can see that the pingd:0 resource has failed once, at Mon Apr 6 11:22:22 2009. ^[12] We also see that the node is connected to three "pingd" peers and that all known resources have been checked for on this machine (probe_complete).

^[12] You can use the following Perl one-liner to print a human readable of any seconds-since-epoch value:

perl -e 'print scalar(localtime($seconds))."\n"'