[Pacemaker] using crm_resource -C when the affected node is down

Lars Marowsky-Bree lmb at suse.de
Fri Feb 6 06:46:22 EST 2009

On 2009-02-06T12:42:15, "Raoul Bhatia [IPAX]" <r.bhatia at ipax.at> wrote:

> > Uhm, but the kind of errors which crm_resource -C would clean up are
> > only relevant for that specific node - which is down. So why does it
> > matter?
> right - but i currently have 53 lines of output (crm_mon -1|wc -l) if
> everything is operating normal. imagine more errors showing up. this
> does not contribute to a better overview.

Perhaps by default crm_mon should not show data from offline nodes,
except possibly an indication whether they are scheduled for fencing
(which, I think, is now available in the CIB).

> > Further, the status section for the node is cleared anyway once it is
> > fenced, no?
> maybe - i cannot tell as i rebootet via:
> > /etc/init.d/heartbeat stop && reboot -fn
> resulting in:
> > Node: wc01 (31de4ab3-2d05-476e-8f9a-627ad6cd94ca): online
> > Node: wc02 (f36760d8-d84a-46b2-b452-4c8cac8b3396): OFFLINE
> so actually, this is a regular stop, right?

Hrm, yes, I would have guessed that this should clean out the status
section - a node which has shut down cleanly has no state worth
remembering (short of "down - clean").


Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

More information about the Pacemaker mailing list