On Wed, Jul 29, 2009 at 4:45 AM, hj lee<kerd...@gmail.com> wrote: > Thank you very much for your reply. > > When I use the heartbeat stack, it takes 3 sec. In the same environment, it > takes less than 1 sec with OpenAIS stack.
Wow, that is quite surprising. Good reason to use OpenAIS then :-) > I am using RHEL 5 rpms from > Pacemaker and Pacemaker 1.0.4. Did any body measure the time takes from > demote to promote on both stacks? I wonder whether other people have the > same result or not. > > Thanks > hj > > On Tue, Jul 28, 2009 at 2:26 AM, Andrew Beekhof <and...@beekhof.net> wrote: >> >> > 2. By using co-location constraint, the time takes from demote to >> > promote is >> > around 3 sec(when notify is enabled) and 1 sec (when notify is >> > disabled). >> > For mission critical application, I think a downtime of 1 or 3 sec is >> > too >> > long. How can I minimize this transition time? >> >> Its purely down to your network and what the resource is doing during >> the promote/demote and notify actions. > > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
