Andrew Beekhof writes:
>
> Yes. If you want the cluster to start things in a particular order,
then you need to specify it.
Andrew, but my issue isn't getting the resources to start in a a
specific order. My issue is that I can't get the slave resource to get
promoted when the previous maste
Dear all,
I configured meta failure-timeout=60sec on all of my resources. For the
sake of simplicity, assume I have a group of two resources FIRST and
SECOND (where SECOND is started after FIRST, surprise!).
If now FIRST crashes, I see a failure, as expected. I also see that
SECOND is stopped, as
The primary goal is to transparently update software in cluster. I
just did HA suite update using simple RPM and observed that RPM
attempts to restart stack (rcopenais try-restart). So
a) if it worked, it would mean resources had been migrated from this
node - interruption
b) it did not work - ap
Thanks!
OK, so I've followed the DRBD steps in the guide all the way till "cib
commit fs" in Section 7.4, right before "Testing Migration". However, when
I do a crm_mon, I get the following "failed actions".
Last updated: Thu Oct 16 17:28:34 2014
Last change: Thu Oct 16 17:26:04 2014 via crm_shad
On 16 Oct 2014, at 7:56 pm, Sahil Aggarwal wrote:
> Sorry, i didn't get your point and i am again re-iterating the problem:
>
> Two Node cluster Node A , Node B .
>
> Service X running on Node A, Node B is DC.
>
> We are using stack corosync with Pacemaker.
> Failure Timeout is 10 sec .
> T
On 16 Oct 2014, at 6:33 pm, Sahil Aggarwal wrote:
> Hello ,
>
> Yes that log might be due to that reason but , it should not ignore the
> resource as it is not taking any action for that resource i..e. not starting
> the resource .
it doesn't know that at the time
>
> and second thing
>
