On Mon, Jan 30, 2012 at 8:01 PM, Florian Crouzat
wrote:
> Le 30/01/2012 01:42, Gruen, Wolfgang a écrit :
>
>
>> > Issuing /etc/init.d/corosync stop or /etc/init.d/pacemaker stop causes
>
>
> On a running cluster, you need to stop pacemaker first, it's mandatory
> AFAIK.
Correct
>
>
> --
> Cheer
Le 30/01/2012 01:42, Gruen, Wolfgang a écrit :
> Issuing /etc/init.d/corosync stop or /etc/init.d/pacemaker stop causes
On a running cluster, you need to stop pacemaker first, it's mandatory
AFAIK.
--
Cheers,
Florian Crouzat
___
Pacemaker maili
We are running a cluster with 15 nodes and are running with 300 resources.
*** Cluster Shutdown Fails
> Issuing /etc/init.d/corosync stop or /etc/init.d/pacemaker stop causes
> nodes to hang
>
>>> Waiting for corosync services to
>>> unload.
On Thu, Nov 04, 2010 at 11:01:29AM +0100, Samuel CUELLA wrote:
> Hi List,
>
> I'm currently trying to implement a complete cluster shutdown to
> react to a 'catastrophic' failure like a power outage.
> The problem is that if I try to shut it down node by nodes,
> resources are migrated. Of course
Hi List,
I'm currently trying to implement a complete cluster shutdown to react
to a 'catastrophic' failure like a power outage.
The problem is that if I try to shut it down node by nodes, resources
are migrated. Of course, this is the correct behavior.
I searched the internet and the offici
