[Openais] Major stability improvements to GMI

[Steven Dake]

The groups.conf file is used with the availability management framework
API.  It defines the components that are used in a service group.  The
service group is used by an application to provide a service in active
standby n+m model.

It doesn't control how many processors can join the ring.  The number of
processors that can belong to a ring is set by the MAX_MEMBERS define at
the top of gmi.c

It is set to 16, although I have only tested 12 processors.

12 processors is very stable and operates correctly, except during
partitions where if packets are lost, bad things can happen.  I know
about this particular problem and how to fix it.

There are no particular roles of any processor.  The only "role" is that
of the ring representative, but that is determined by the ring algorithm
and cannot be controlled.

Thanks
-steve

On Wed, 2004-07-14 at 17:27, Sabharwal, Atul wrote:
> Steve,
> 
> If you could point me regarding how to tweak the groups.conf file.
> Does this file control how many nodes can join the ring as well
> As their roles.
> 
> Thanks,
> 
> Atul
> 
> >-----Original Message-----
> >From: openais-bounces at lists.osdl.org 
> >[mailto:openais-bounces at lists.osdl.org] On Behalf Of Steven Dake
> >Sent: Wednesday, July 14, 2004 5:07 PM
> >To: openais at lists.osdl.org
> >Subject: [Openais] Major stability improvements to GMI
> >
> >The fragmentation and assembly of messages greater then 1472 bytes in
> >length in GMI has been prone to crashes and not making forward progress
> >with multiple senders.
> >
> >This functionality has been redesigned and is now alot more stable.  If
> >you tried out openais in the past and it behaved poorly under 
> >stress for
> >you, try it out now and report any sorts of problems you see.
> >
> >Thanks!
> >-steve
> >
> >
> >