[Openais] status of code in bk?
kjsmith at nortel.com
Wed Feb 9 16:41:32 PST 2005
One thing I notice when running the latest bitkeeper code is that the time
it takes to notice that another node has failed has increased. If I start up
2 aisexecs (one on each node) and then ctrl-c one of them, the other takes a
few seconds to notice that the node went away. When we started using the
totem-ais code in Jan, I was impressed that the time to notice the failure
was decreased (almost instaneous) than it had been with the previous
openais, but now it seems like it is slower than with the previous openais
(before the totem changes).
Are there new configuration parms that I need to muck with to get the node
failure detection time down? (I did see your email a while back on
decreasing this time, I was just wondering if you had intended to make the
detection time greater in this new code).
From: Steven Dake [mailto:sdake at mvista.com]
Sent: Tuesday, February 08, 2005 3:29 PM
To: Smith, Kristen [NGC:B675:EXCH]
Cc: openais at lists.osdl.org; Bajpai, Muni [NGC:B670:EXCH]
Subject: Re: [Openais] status of code in bk?
All of the code is now in bitkeeper. I'll try to wrap up a freshmeat
release tomorrow with code coverage reports after running the tests we have
On Tue, 2005-02-08 at 07:30, Kristen Smith wrote:
> Could you please tell me the status of the latest code that is in
> bitkeeper? Does it have all the patches you guys have been putting out
> for the past few weeks? If not, when do you foresee updating it with
> all these patches?
> Openais mailing list
> Openais at lists.osdl.org http://lists.osdl.org/mailman/listinfo/openais
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openais