Hi,
I agree with Alan, if this part of work goes into a quorum module, it
would be perfect.
Quorum module is a kind of plugin too, so it is not an internal
behavior of heartbeat.
When a split-brain happened, the side with more nodes will take the
quorum and continue the service, the less nodes si
> 2007/8/10, Junko IKEDA <[EMAIL PROTECTED]>:
> > Hi,
> >
> > sfex_lock.c would work like this;
> > 1) read lock data
> > 2) check current lock status
> > 3) reserve lock
> > 4) detect the collision of lock
> > 5) extension of lock
> > 6) lock acquisition completion
> >
> > in "reserve lock" phase,
2007/8/13, Junko IKEDA <[EMAIL PROTECTED]>:
> > 2007/8/10, Junko IKEDA <[EMAIL PROTECTED]>:
> > > Hi,
> > >
> > > sfex_lock.c would work like this;
> > > 1) read lock data
> > > 2) check current lock status
> > > 3) reserve lock
> > > 4) detect the collision of lock
> > > 5) extension of lock
> > >
> > Assume we have 2 nodes.
> > 1. Node A & B reach step 3) in the same time.
> > 2. sfex_lock on Node B is scheduled out due to some other reasons.
> > 3. sfex_lock on Node A goes through step 3 to 6, and Node A holds
> > the lock now.
Node A is sure to hold the lock at this moment.
sfex_lock()
2007/8/13, Junko IKEDA <[EMAIL PROTECTED]>:
> > > Assume we have 2 nodes.
> > > 1. Node A & B reach step 3) in the same time.
> > > 2. sfex_lock on Node B is scheduled out due to some other reasons.
> > > 3. sfex_lock on Node A goes through step 3 to 6, and Node A holds
> > > the lock now.
>
> Node
