> OK. I think you are mis-understanding the problem.
>
> When the communication between Node A & B is fine, you don't need any
> kind of lock. Heartbeat itself can ensure the resource runs on one
selected
> node, and on one node only.
sfex_lock() is just checking the status that shows which node
Just a quick note to say that the packages at
http://software.opensuse.org/download/server:/ha-clustering
were refreshed today after passing automated testing.
The current version is 2.1.2-1.1 for .rpm and 2.1.0-1 for .deb
Some stats on the changes since the previous build (e3c9306b9223):
DAIKI MATSUDA wrote:
> Hi, All
>
> I add the new function for heartbeat-2.0.8 and attached its patch file.
>
> The function is to apply the new timeout parameters ( keepalive,
> deadtime, deadping, warntime ) without stopping the heartbeat services.
> Currently heartbeat
Hi,
Thank you for your comment.
We will check the operation and source code of the quorum
plugin from now.
Thanks,
OKADA Satoshi
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
be
2007/8/13, Junko IKEDA <[EMAIL PROTECTED]>:
> > > If Node B updates the lock status _at just the right moment_,
> > > sfex_update() detects that the other node is trying to update its
> status,
> > > and it will be terminated with exit(2).
> > This time window is enough to destroy all data if you a
> > If Node B updates the lock status _at just the right moment_,
> > sfex_update() detects that the other node is trying to update its
status,
> > and it will be terminated with exit(2).
> This time window is enough to destroy all data if you are bad luck ;-(
Node B is just updating its lock stat
