[Spread-users] How to detect if a Spread node fails
jschultz at spreadconcepts.com
Wed Jul 13 12:20:35 EDT 2011
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.
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:
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
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 ?
Email: andrew.holt at 4asolutions.co.uk
De Omnibus Dubitandum
Spread-users mailing list
Spread-users at lists.spread.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3805 bytes
Desc: not available
Url : http://lists.spread.org/pipermail/spread-users/attachments/20110713/1dc38410/attachment.bin
More information about the Spread-users