[Pacemaker] Pengine behavior

[Виталий Давудов]

Hi, list!

I have configured cluster for voip application.
Here my configuration:

# crm configure show
node $id="552f91eb-e70a-40a5-ac43-cb16e063fdba" freeswitch1 \
         attributes standby="off"
node $id="c86ab64d-26c4-4595-aa32-bf9d18f714e7" freeswitch2 \
         attributes standby="off"
primitive FailoverIP1 ocf:heartbeat:IPaddr2 \
         params iflabel="FoIP1" ip="91.211.219.142" cidr_netmask="30" 
nic="eth1.50" \
         op monitor interval="1s"
primitive FailoverIP2 ocf:heartbeat:IPaddr2 \
         params iflabel="FoIP2" ip="172.30.0.1" cidr_netmask="16" 
nic="eth1.554" \
         op monitor interval="1s"
primitive FailoverIP3 ocf:heartbeat:IPaddr2 \
         params iflabel="FoIP3" ip="10.18.1.1" cidr_netmask="24" 
nic="eth1.552" \
         op monitor interval="1s"
primitive fs lsb:FSSofia \
         op monitor interval="1s" enabled="false" timeout="2s" 
on-fail="standby" \
         meta target-role="Started"
group HAServices FailoverIP1 FailoverIP2 FailoverIP3 \
         meta target-role="Started"
order FS-after-IP inf: HAServices fs
property $id="cib-bootstrap-options" \
         dc-version="1.0.12-unknown" \
         cluster-infrastructure="Heartbeat" \
         stonith-enabled="false" \
         expected-quorum-votes="1" \
         no-quorum-policy="ignore" \
         last-lrm-refresh="1299964019"
rsc_defaults $id="rsc-options" \
         resource-stickiness="100"

When 1-st node was crashed, then 2-nd node become active. During this 
process in ha-debug file I found lines:

...
Jul 06 17:16:42 freeswitch1 crmd: [3385]: info: start_subsystem: 
Starting sub-system "pengine"
Jul 06 17:16:42 freeswitch1 pengine: [3675]: info: Invoked: 
/usr/lib64/heartbeat/pengine
*Jul 06 17:16:42 freeswitch1 pengine: [3675]: info: main: Starting pengine
Jul 06 17:16:46 freeswitch1 crmd: [3385]: info: do_dc_takeover: Taking 
over DC status for this partition*
Jul 06 17:16:46 freeswitch1 cib: [3381]: info: cib_process_readwrite: We 
are now in R/W mode
Jul 06 17:16:46 freeswitch1 cib: [3381]: info: cib_process_request: 
Operation complete: op cib_master for section 'all' 
(origin=local/crmd/11, version=0.391.20): ok (
  rc=0)
Jul 06 17:16:46 freeswitch1 cib: [3381]: info: cib_process_request: 
Operation complete: op cib_modify for section cib (origin=local/crmd/12, 
version=0.391.20): ok (rc
  =0)
Jul 06 17:16:46 freeswitch1 cib: [3381]: info: cib_process_request: 
Operation complete: op cib_modify for section crm_config 
(origin=local/crmd/14, version=0.391.20):
   ok (rc=0)
...

After "Starting pengine", only thru 4 seconds occured next action. What 
happens at this time? Is it possible to reduce this time?

Thanks in advance.

-- 
Best regards,
Vitaly

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120711/602cf538/attachment-0003.html>