On Tue, Dec 15, 2009 at 5:56 PM, Steven Dake <[email protected]> wrote:
> > 500 msec should work but depends on your environment. More details > below. > > The timers are close to those specified (500msec+the tick time of your > kernel). Most kernels have a tick time of 10 msec or less. (The HZ > kernel variable). I am not sure about tickless kernels. > > I regularly run corosync with 200 msec token timeout. It works very > well as long corosync is regularly scheduled. realtime processes and > kernel misbehavior (kernel spinning in a loop with spinlock held) can > prevent corosync from being scheduled in a timely fashion, so it all > depends on your deployment environment. > > The kernel option CONFIG_PREEMPT helps since it will cause corosync to > preempt other long running processes in the system. > > Thank you very much for your response. This will be a good starting point. Would you give some hint for other parameters like token_retransmits or consensus when you use 200msec token timeout? Is the latest Wilson faster than Whitetank version for power off detection? or they are same? hj
_______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
