final class ClusterClientSettings extends NoSerializationVerificationNeeded
- Annotations
- @deprecated
- Deprecated
(Since version 2.6.0) Use Akka gRPC instead, see https://doc.akka.io/libraries/akka-core/2.6/cluster-client.html#migration-to-akka-grpc
- Source
- ClusterClient.scala
- Alphabetic
- By Inheritance
- ClusterClientSettings
- NoSerializationVerificationNeeded
- AnyRef
- Any
- by any2stringadd
- by StringFormat
- by Ensuring
- by ArrowAssoc
- Hide All
- Show All
- Public
- Protected
Instance Constructors
- new ClusterClientSettings(initialContacts: Set[ActorPath], establishingGetContactsInterval: FiniteDuration, refreshContactsInterval: FiniteDuration, heartbeatInterval: FiniteDuration, acceptableHeartbeatPause: FiniteDuration, bufferSize: Int)
For binary/source compatibility
- new ClusterClientSettings(initialContacts: Set[ActorPath], establishingGetContactsInterval: FiniteDuration, refreshContactsInterval: FiniteDuration, heartbeatInterval: FiniteDuration, acceptableHeartbeatPause: FiniteDuration, bufferSize: Int, reconnectTimeout: Option[FiniteDuration])
- initialContacts
Actor paths of the
ClusterReceptionist
actors on the servers (cluster nodes) that the client will try to contact initially. It is mandatory to specify at least one initial contact. The path of the default receptionist is "akka://system@hostname:port/system/receptionist"- establishingGetContactsInterval
Interval at which the client retries to establish contact with one of ClusterReceptionist on the servers (cluster nodes)
- refreshContactsInterval
Interval at which the client will ask the
ClusterReceptionist
for new contact points to be used for next reconnect.- heartbeatInterval
How often failure detection heartbeat messages for detection of failed connections should be sent.
- acceptableHeartbeatPause
Number of potentially lost/delayed heartbeats that will be accepted before considering it to be an anomaly. The ClusterClient is using the akka.remote.DeadlineFailureDetector, which will trigger if there are no heartbeats within the duration
heartbeatInterval + acceptableHeartbeatPause
.- bufferSize
If connection to the receptionist is not established the client will buffer this number of messages and deliver them the connection is established. When the buffer is full old messages will be dropped when new messages are sent via the client. Use 0 to disable buffering, i.e. messages will be dropped immediately if the location of the receptionist is unavailable.
- reconnectTimeout
If the connection to the receptionist is lost and cannot be re-established within this duration the cluster client will be stopped. This makes it possible to watch it from another actor and possibly acquire a new list of initialContacts from some external service registry
Value Members
- val acceptableHeartbeatPause: FiniteDuration
- val bufferSize: Int
- val establishingGetContactsInterval: FiniteDuration
- val heartbeatInterval: FiniteDuration
- val initialContacts: Set[ActorPath]
- val reconnectTimeout: Option[FiniteDuration]
- val refreshContactsInterval: FiniteDuration
- def withBufferSize(bufferSize: Int): ClusterClientSettings
- def withEstablishingGetContactsInterval(establishingGetContactsInterval: FiniteDuration): ClusterClientSettings
- def withHeartbeat(heartbeatInterval: FiniteDuration, acceptableHeartbeatPause: FiniteDuration): ClusterClientSettings
- def withInitialContacts(initialContacts: Set[ActorPath]): ClusterClientSettings
Java API
- def withInitialContacts(initialContacts: Set[ActorPath]): ClusterClientSettings
Scala API
- def withReconnectTimeout(reconnectTimeout: Option[FiniteDuration]): ClusterClientSettings
- def withRefreshContactsInterval(refreshContactsInterval: FiniteDuration): ClusterClientSettings