JGroups Protocol VERIFY SUSPECT: Difference between revisions
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
The protocol works as follows: it catches SUSPECT events traveling up the stack. Verifies that the suspected member is really dead. If yes, passes SUSPECT event up the stack, otherwise discards it. Has to be placed somewhere above the [FD] layer and below the [GMS] layer (receiver of the SUSPECT event). Note that SUSPECT events may be reordered by this protocol. | The protocol works as follows: it catches SUSPECT events traveling up the stack. Verifies that the suspected member is really dead. If yes, passes SUSPECT event up the stack, otherwise discards it. Has to be placed somewhere above the [FD] layer and below the [GMS] layer (receiver of the SUSPECT event). Note that SUSPECT events may be reordered by this protocol. | ||
=Suspect Verification= | |||
!!!Configuration Sample | !!!Configuration Sample | ||
Revision as of 03:20, 3 March 2016
External
- VERIFY_SUSPECT manual page http://www.jgroups.org/manual/index.html#_verify_suspect
- JGroups Wiki http://community.jboss.org/wiki/JGroupsVERIFYSUSPECT
Internal
Overview
Verifies that a suspected member is really dead by pinging that member once again. Drops suspect message if member does respond. Tries to minimize false suspicions.
The protocol works as follows: it catches SUSPECT events traveling up the stack. Verifies that the suspected member is really dead. If yes, passes SUSPECT event up the stack, otherwise discards it. Has to be placed somewhere above the [FD] layer and below the [GMS] layer (receiver of the SUSPECT event). Note that SUSPECT events may be reordered by this protocol.
Suspect Verification
!!!Configuration Sample
{{{
<VERIFY_SUSPECT timeout="1500"/>
}}}
!!!Periodic Scans
VERIFY_SUSPECT starts an internal thread ("VERIFY_SUSPECT.TimerThread") when a suspect is added to the suspect table. The thread continually iterates over the entries and removes entries whose time have elapsed. For each removed entry, a SUSPECT event is passed up the stack (because elapsed time means verification of member's liveness failed). Computes the shortest time to wait (min of all timeouts) and waits(time) ms. Will be woken up when entry is removed (in case of successful verification of that member's liveness). Terminates when no entry remains in the table.
__Referenced by:__\\ [{INSERT com.ecyrd.jspwiki.plugin.ReferringPagesPlugin WHERE max=20, maxwidth=50}]