Re: How to detect if a Spread node fails

Have at least one process per daemon join the groups in which you are interested in tracking.  Track the membership of the group.  If you see a caused by network where all the *#able members leave, then its a good bet that daemon has either crashed or partitioned away.

If that's not good enough then you might be able to administratively, through code changes, get a report of the actual daemon membership which can tell you if able is in the daemon membership or not.

Cheers!

-----
John Lane Schultz
Spread Concepts LLC
Phn: 301 830 8100
Cell: 443 838 2200

On Jul 13, 2011, at 11:27 AM, Andrew Holt wrote:

Hi,

I have two machines each running the spread server, and each setup so they know about each other.  Let’s call them able & baker.

I have a number of clients programs, in the same group on each

So: 

#fred#able
#joe#able
#bill#baker
#who#baker

If spread dies, is killed or a machine dies how can I detect that the node has gone ‘offline’ ?

baker receives a message of the type Is_caused_network_mess for each group.  What I need is to know the source is 'able’ 

Any hints ?

Thanks,
Andrew

=============================
Andrew Holt

Email: [email protected]

De Omnibus Dubitandum
=============================




_______________________________________________
Spread-users mailing list
[email protected]
http://lists.spread.org/mailman/listinfo/spread-users

_______________________________________________
Spread-users mailing list
[email protected]
http://lists.spread.org/mailman/listinfo/spread-users