All Classes and Interfaces
Class
Description
An interface for sending protocol messages from the cluster coordinator to nodes.
A wrapper class for consolidating a protocol sender and listener for the
cluster manager.
Responsible for coordinating nodes in the cluster
A node's request to connect to the cluster.
The cluster manager's response to a node's connection request.
An enumeration of the reasons that a node may be disconnected
from the cluster
Framework Cluster Protocol Configuration with components supporting cluster communication
A heartbeat for indicating the status of a node to the cluster.
A HeartbeatMonitor is responsible for monitoring some remote resource for heartbeats from each
node in a cluster and reacting to those heartbeats (or lack thereof).
The payload of the heartbeat.
Implements a context for communicating internally amongst the cluster using
JAXB.
Wraps a protocol message and an identifier for sending the message by way
multicast.
Describes the current status of a node
A node identifier denoting the coordinates of a flow controller that is
connected to a cluster.
An interface for sending protocol messages from a node to the cluster
manager.
Message to indicate that the status of a node in the cluster has changed
An enumeration of the reasons that a node may be offloaded
The context for communicating using the internal cluster protocol.
The base exception for problems encountered while communicating within the
cluster.
A handler for processing protocol messages.
Defines the interface for a listener to process protocol messages.
Defines a marshaller for serializing protocol messages.
Defines an unmarshaller for deserializing protocol messages.
This message is used an "ACK" for a ReconnectionRequestMessage
Implements a listener for TCP/IP messages sent over unicast socket.
Implements a listener for protocol messages sent over unicast socket.
A protocol sender for sending protocol messages from the cluster manager to
nodes.
Represents a dataflow, which includes the raw bytes of the flow.xml and
whether processors should be started automatically at application startup.
Represents the exceptional case when a service's address is not known.