On 3 November 2010 11:31, Dejan Muhamedagic <[email protected]> wrote: > Hi, > > On Wed, Nov 03, 2010 at 11:16:14AM +0100, Pavlos Parissis wrote: >> On 3 November 2010 07:31, Alain.Moulle <[email protected]> wrote: >> > Hi, >> > >> > If you execute a crm action (whatever action) on a resource, let's say >> > for example a stop ... on res1, >> > and if just after , you execute whatever other crm action on another >> > resource , for example >> > a stop on res2, there is always a delay of a few seconds (about 20 to >> > 30s) before the second >> > action is completed. > > I wouldn't say "a few" for 20-30 seconds. Which is it? > >> > I wonder if it is normal, if it is due to resources management inside >> > pacemaker ? > > Depends on your resources. Actions on independent resources > should run in parallel. However, if the pacemaker already > started a transition (i.e. a set of actions triggered by > "resource stop"), then it may wait for it to finish first, > before executing another transition.
You are right, it my case it was so fast that I never show a delay. I did a test and the start of sshd_02 was trigger after the start of sshd_01 was confirmed. look bellow running crm resource start sshd_01 and crm resource start sshd_02 almost on parallel r...@admin:/var/log# tail -f daemon.log|egrep 'do_lrm_rsc_op: Performing key|confirmed on' Nov 3 12:09:35 node-01 crmd: [3332]: info: do_lrm_rsc_op: Performing key=20:12:0:b341e009-64b0-4732-b6e0-c5843a148c75 op=sshd_01_start_0 ) Nov 3 12:09:37 node-03 crmd: [3363]: info: match_graph_event: Action sshd_01_start_0 (20) confirmed on node-01 (rc=0) Nov 3 12:09:38 node-01 crmd: [3332]: info: do_lrm_rsc_op: Performing key=22:13:0:b341e009-64b0-4732-b6e0-c5843a148c75 op=sshd_01_monitor_600000 ) Nov 3 12:09:38 node-01 crmd: [3332]: info: do_lrm_rsc_op: Performing key=23:13:0:b341e009-64b0-4732-b6e0-c5843a148c75 op=mailAlert-01_start_0 ) Nov 3 12:09:38 node-02 crmd: [3384]: info: do_lrm_rsc_op: Performing key=35:13:0:b341e009-64b0-4732-b6e0-c5843a148c75 op=sshd_02_start_0 ) Nov 3 12:09:40 node-03 crmd: [3363]: info: match_graph_event: Action sshd_01_monitor_600000 (22) confirmed on node-01 (rc=0) Nov 3 12:09:40 node-03 crmd: [3363]: info: match_graph_event: Action mailAlert-01_start_0 (23) confirmed on node-01 (rc=0) Nov 3 12:09:40 node-03 crmd: [3363]: info: match_graph_event: Action sshd_02_start_0 (35) confirmed on node-02 (rc=0) Nov 3 12:09:41 node-02 crmd: [3384]: info: do_lrm_rsc_op: Performing key=36:13:0:b341e009-64b0-4732-b6e0-c5843a148c75 op=sshd_02_monitor_600000 ) Nov 3 12:09:41 node-02 crmd: [3384]: info: do_lrm_rsc_op: Performing key=37:13:0:b341e009-64b0-4732-b6e0-c5843a148c75 op=mailAlert-02_start_0 ) Nov 3 12:09:42 node-01 crmd: [3332]: info: do_lrm_rsc_op: Performing key=24:13:0:b341e009-64b0-4732-b6e0-c5843a148c75 op=mailAlert-01_monitor_2000 ) Nov 3 12:09:42 node-03 crmd: [3363]: info: match_graph_event: Action sshd_02_monitor_600000 (36) confirmed on node-02 (rc=0) Nov 3 12:09:42 node-03 crmd: [3363]: info: match_graph_event: Action mailAlert-02_start_0 (37) confirmed on node-02 (rc=0) Nov 3 12:09:43 node-03 crmd: [3363]: info: match_graph_event: Action mailAlert-01_monitor_2000 (24) confirmed on node-01 (rc=0) Nov 3 12:09:44 node-02 crmd: [3384]: info: do_lrm_rsc_op: Performing key=38:13:0:b341e009-64b0-4732-b6e0-c5843a148c75 op=mailAlert-02_monitor_2000 ) Nov 3 12:09:46 node-03 crmd: [3363]: info: match_graph_event: Action mailAlert-02_monitor_2000 (38) confirmed on node-02 (rc=0) >> No, it is not normal. I have several resources on different groups and >> I can't independently stop/start them without waiting. > > That's odd. > Please ignore my last statement and sorry for writing wrong things. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
