Number of potentially lost/delayed heartbeats that will be accepted before considering it to be an anomaly. The ClusterClient is using the DeadlineFailureDetector, which will trigger if there are no heartbeats within the duration HeartbeatInterval + AcceptableHeartbeatPause.

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.

Interval at which the client retries to establish contact with one of ClusterReceptionist on the servers (cluster nodes)

How often failure detection heartbeat messages for detection of failed connections should be sent.

Actor paths of the ClusterReceptionist actors on the servers (cluster nodes) that the client will try to contact initially.

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

Interval at which the client will ask the ClusterReceptionist for new contact points to be used for next reconnect.