Class HazelcastClusterMulticastProperties
java.lang.Object
org.apereo.cas.configuration.model.support.hazelcast.HazelcastClusterMulticastProperties
- All Implemented Interfaces:
Serializable
@RequiresModule(name="cas-server-support-hazelcast-core")
public class HazelcastClusterMulticastProperties
extends Object
implements Serializable
This is
HazelcastClusterMulticastProperties
.- Since:
- 5.2.0
- See Also:
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptiongetGroup()
The multicast group address used for discovery.int
getPort()
The multicast port used for discovery.int
specifies the time in seconds that a member should wait for a valid multicast response from another member running in the network before declaring itself the leader member (the first member joined to the cluster) and creating its own cluster.int
Gets the time to live for the multicast package in seconds.Multicast trusted interfaces for discovery.boolean
Enables a multicast configuration using a group address and port.setEnabled
(boolean enabled) Enables a multicast configuration using a group address and port.The multicast group address used for discovery.setPort
(int port) The multicast port used for discovery.setTimeout
(int timeout) specifies the time in seconds that a member should wait for a valid multicast response from another member running in the network before declaring itself the leader member (the first member joined to the cluster) and creating its own cluster.setTimeToLive
(int timeToLive) Gets the time to live for the multicast package in seconds.setTrustedInterfaces
(String trustedInterfaces) Multicast trusted interfaces for discovery.
-
Constructor Details
-
HazelcastClusterMulticastProperties
public HazelcastClusterMulticastProperties()
-
-
Method Details
-
getTrustedInterfaces
Multicast trusted interfaces for discovery. With the multicast auto-discovery mechanism, Hazelcast allows cluster members to find each other using multicast communication. The cluster members do not need to know the concrete addresses of the other members, as they just multicast to all the other members for listening. Whether multicast is possible or allowed depends on your environment. -
getGroup
The multicast group address used for discovery. With the multicast auto-discovery mechanism, Hazelcast allows cluster members to find each other using multicast communication. The cluster members do not need to know the concrete addresses of the other members, as they just multicast to all the other members for listening. Whether multicast is possible or allowed depends on your environment. -
getPort
public int getPort()The multicast port used for discovery. -
getTimeout
public int getTimeout()specifies the time in seconds that a member should wait for a valid multicast response from another member running in the network before declaring itself the leader member (the first member joined to the cluster) and creating its own cluster. This only applies to the startup of members where no leader has been assigned yet. If you specify a high value, such as 60 seconds, it means that until a leader is selected, each member will wait 60 seconds before moving on. Be careful when providing a high value. Also, be careful not to set the value too low, or the members might give up too early and create their own cluster. -
getTimeToLive
public int getTimeToLive()Gets the time to live for the multicast package in seconds. This is the default time-to-live for multicast packets sent out on the socket -
isEnabled
public boolean isEnabled()Enables a multicast configuration using a group address and port. Contains the configuration for the multicast discovery mechanism. With the multicast discovery mechanism Hazelcast allows Hazelcast members to find each other using multicast. So Hazelcast members do not need to know concrete addresses of members, they just multicast to everyone listening. It depends on your environment if multicast is possible or allowed; otherwise you need to have a look at the tcp/ip cluster -
setTrustedInterfaces
Multicast trusted interfaces for discovery. With the multicast auto-discovery mechanism, Hazelcast allows cluster members to find each other using multicast communication. The cluster members do not need to know the concrete addresses of the other members, as they just multicast to all the other members for listening. Whether multicast is possible or allowed depends on your environment.- Returns:
this
.
-
setGroup
The multicast group address used for discovery. With the multicast auto-discovery mechanism, Hazelcast allows cluster members to find each other using multicast communication. The cluster members do not need to know the concrete addresses of the other members, as they just multicast to all the other members for listening. Whether multicast is possible or allowed depends on your environment.- Returns:
this
.
-
setPort
The multicast port used for discovery.- Returns:
this
.
-
setTimeout
specifies the time in seconds that a member should wait for a valid multicast response from another member running in the network before declaring itself the leader member (the first member joined to the cluster) and creating its own cluster. This only applies to the startup of members where no leader has been assigned yet. If you specify a high value, such as 60 seconds, it means that until a leader is selected, each member will wait 60 seconds before moving on. Be careful when providing a high value. Also, be careful not to set the value too low, or the members might give up too early and create their own cluster.- Returns:
this
.
-
setTimeToLive
Gets the time to live for the multicast package in seconds. This is the default time-to-live for multicast packets sent out on the socket- Returns:
this
.
-
setEnabled
Enables a multicast configuration using a group address and port. Contains the configuration for the multicast discovery mechanism. With the multicast discovery mechanism Hazelcast allows Hazelcast members to find each other using multicast. So Hazelcast members do not need to know concrete addresses of members, they just multicast to everyone listening. It depends on your environment if multicast is possible or allowed; otherwise you need to have a look at the tcp/ip cluster- Returns:
this
.
-