View on GitHub
PingResponseDirective Enumeration Reference
PingResponseDirective
public enum PingResponseDirectiveDirects a shell implementation about how to handle an incoming .pingRequest.
-
Indicates that incoming gossip was processed and the membership may have changed because of it, inspect the
GossipProcessedDirectiveto learn more about what change was applied.Declaration
Swift
case gossipProcessed(GossipProcessedDirective) -
Upon receiving an
ackfromtarget, if we were making this ping because of apingRequestfrompeer, we need to forward that acknowledgement to that peer now.Declaration
Swift
case sendAck(peer: SWIMPingRequestOriginPeer, acknowledging: SWIM.SequenceNumber, target: SWIMPeer, incarnation: UInt64, payload: SWIM.GossipPayload)Parameters
tothe peer to which an
ackshould be sentpingedTargetthe
myselfpeer, should be passed astargetwhen sending the ack messageincarnationthe incarnation number of this peer; used to determine which status is “the latest” when comparing acknowledgement with suspicions
payloadadditional gossip payload to include in the ack message
acknowledgingsequence number of the ack message
-
Send a
nackto thepeerwhich originally send this peer request.Declaration
Swift
case sendNack(peer: SWIMPingRequestOriginPeer, acknowledging: SWIM.SequenceNumber, target: SWIMPeer)Parameters
peerthe peer to which the
nackshould be sentacknowledgingsequence number of the ack message
targetthe peer which we attempted to ping but it didn’t reply on time
-
Send a
pingRequestas described by theSendPingRequestDirective.The target node did not reply with an successful
.ackand as such was now marked as.suspect. By sending ping requests to other members of the cluster we attempt to revert this suspicion, perhaps some other node is able to receive an.ackfrom it after all?Declaration
Swift
case sendPingRequests(SendPingRequestDirective)