[Pacemaker] Should monitor operations be stopped after a resource is unmanaged?
Ron Kerry
rkerry at sgi.com
Fri Apr 1 22:09:40 CEST 2011
On 7/22/64 2:59 PM, Pavel Levshin wrote:
> 01.04.2011 18:36, Ron Kerry:
> > Folks -
> >
> > Consider a running cluster with all resources managed. We want to stop
> > and quickly restart a particular resource without impacting other
> > resources. The software stack running on the system can deal with this
> > sort of temporary outage. We perform the following actions:
> > * unmanage the resource
> > * stop the resource
> > * start the resource
> > * manage the resource
> >
> > The above procedure is sometimes successful. However, we will also
> > sometimes get a resource monitor failure after stopping the resource.
> > It is clear that the monitor operation was not stopped (at least not
> > immediately) by unmanaging the resource.
>
> Unmanaged resource cannot be started and stopped, but can still be
> monitored.
So unmanaged really means the resource is still being managed to some degree?
This does not seem desirable behavior. An unmanaged resource should be exactly that ... completely
unmanaged ==> It cannot be stopped, started OR monitored.
--
Ron Kerry rkerry at sgi.com
Global Product Support - SGI Federal
More information about the Pacemaker
mailing list