Interface Cluster.MemberTimeoutAction
-
- All Superinterfaces:
Action
- Enclosing interface:
- Cluster
public static interface Cluster.MemberTimeoutAction extends Action
MemberTimeoutAction is taken by the cluster service to remove members from the cluster who have exceeded a network timeout (e.g. packet-timeout).A MemberTimeoutAction object is valid only for the duration of an invocation to
ActionPolicy.isAllowed(com.tangosol.net.Service, com.tangosol.net.Action)
.Note: ActionPolicy implementations should assume that the effects of a given physical outage may not be detected in an atomic fashion.
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method Description Set<Member>
getAnnouncingMemberSet()
Return the set of Members who are "announcing".long
getIncidentStartTime()
Return the time at which the current outage "incident" was first detected.Set<Member>
getResponsiveMemberSet()
Return the set of Members that have recently responded to this member.Set<Member>
getTimedOutMemberSet()
Return the set of Members that have exceeded their timeout.
-
-
-
Method Detail
-
getTimedOutMemberSet
Set<Member> getTimedOutMemberSet()
Return the set of Members that have exceeded their timeout.- Returns:
- the set of Members that have exceeded their timeout
-
getResponsiveMemberSet
Set<Member> getResponsiveMemberSet()
Return the set of Members that have recently responded to this member.Note: inclusion in the set of responsive members is meaningful, but exclusion is not. Implementations should take care not to infer meaning in members not appearing in the responsive set.
- Returns:
- the set of Members that are known to be healthy
-
getAnnouncingMemberSet
Set<Member> getAnnouncingMemberSet()
Return the set of Members who are "announcing". Announcing members are potential new cluster members who are broadcasting their presence and attempting to join the cluster.- Returns:
- the set of Members who are announcing
-
getIncidentStartTime
long getIncidentStartTime()
Return the time at which the current outage "incident" was first detected. An "incident" is considered to start when the first member timeout is reported, and lasts until no timed-out members remain in the cluster.Note: ActionPolicy implementations should not make assumptions about the time period within which physical outages will be detected, nor should they assume that outages will be reported simultaneously on different members.
- Returns:
- the time in ms at which the current incident started
-
-