This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag


About Us

Contact Us

Legal Info

How To Contribute

Security Issues

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.
To get rid of this notice, you may want to browse the old wiki instead.

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2019-12-10 01:38:01

14) LarsMarowskyBree: Discussion of the states which resources can be in.

  • I suggest that a resource can be in any of the following states (as exposed to an LRM client querying the resource state):
    • stopped
      • start command will lead to starting state

    • starting
      • If no failures occur, will lead to started

      • If a start failure occurs, will lead to failed

    • started
      • Will stick in this state unless monitor ever fails, in which case it will go to failed

    • failed
      • stop command will transition to stopping

      • restart will transition to restarting

    • restarting
      • If no failures occur, will lead to started

      • If a failure occurs, will lead to failed again

    • stopping
      • If no failure occurs, will lead to stopped

      • If a failure occurs, will lead to dead

    • dead

      • This state is special in that no recovery is possible without rebooting the node. It's the dead-end.

    From the ClusterResourceManager perspective, the distinction between starting and started is important, because during a recovery phase we may find a resource in starting phase and know that we can't do anything yet before it has reached the started stage. (Same for the other transitions.) It may also be possible that other resources - ie, primary/secondary-types - can be in more states, transitioning from active to backup or vice-versa, and resources which can be active on a pool of nodes also need to be able to tell that they are number X from a pool of N et cetera. This too needs more thought.

    AlanRobertson had an extended conversation with LarsMarowskyBree on this topic this morning (2/19/2004). We agreed that the LocalResourceManager will not track past resource state. As a result of this conversation, AlanRobertson will mark this item as resolved.