I have two node cluster with single master/slave resource (replicated
database) using pacemaker+openais on SLES11 SP3 (pacemaker
1.1.11-3ca8c3b). I hit weird situation that I did not see before, and
I cannot really understand it. Assuming master runs on node A and
slave runs on node B. If I stop
try to use interleave meta attribute in your clone definition
http://www.hastexo.com/resources/hints-and-kinks/interleaving-pacemaker-clones
2014-09-28 9:56 GMT+02:00 Andrei Borzenkov arvidj...@gmail.com:
I have two node cluster with single master/slave resource (replicated
database) using
В Sun, 28 Sep 2014 13:03:08 +0200
emmanuel segura emi2f...@gmail.com пишет:
try to use interleave meta attribute in your clone definition
http://www.hastexo.com/resources/hints-and-kinks/interleaving-pacemaker-clones
I appreciate if you could elaborate a bit more here. The above link
Hi
Is this normal logging ?
Not sure if I need to investigate any thing
Sep 29 11:35:15 gsdmz1 crmd[2481]: notice: do_state_transition: State
transition S_IDLE - S_POLICY_ENGINE [ input=I_PE_CALC cause=C_TIMER_POPPED
origin=crm_timer_popped ]
Sep 29 11:35:15 gsdmz1 pengine[2480]: notice:
Hi Alex,
Because recheck_timer moves by default every 15 minutes, state transition is
calculated in pengine.
-
{ XML_CONFIG_ATTR_RECHECK, cluster_recheck_interval, time,
Zero disables polling. Positive values are an interval in seconds (unless
other SI units are specified. eg. 5min),
Cool, thanks
Thought it might have been a normal check.
A
-Original Message-
From: renayama19661...@ybb.ne.jp
[mailto:renayama19661...@ybb.ne.jp]
Sent: Monday, 29 September 2014 12:20 PM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] query ?
Hi Alex,