$ref: #/definitions/Import

$ref: #/definitions/ConfigReplacers

$ref: #/definitions/ManagementCenter

description: The "properties" mapping lets you add properties to some of the Hazelcast elements used to configure some of the Hazelcast modules. You can define the name and value of these properties. You can use "properties" for the following Hazelcast configuration elements: \n * discovery-strategy \n * map-store \n * queue-store \n * wan-replication \n * ssl \n * service \n * login-module \n * security-object \n * socket-interceptor

$ref: #/definitions/WanReplication

$ref: #/definitions/Network

$ref: #/definitions/PartitionGroup

$ref: #/definitions/ExecutorService

$ref: #/definitions/DurableExecutorService

$ref: #/definitions/ScheduledExecutorService

$ref: #/definitions/CardinalityEstimator

$ref: #/definitions/Queue

$ref: #/definitions/Map

$ref: #/definitions/Multimap

$ref: #/definitions/ReplicatedMap

$ref: #/definitions/Cache

$ref: #/definitions/List

$ref: #/definitions/Set

$ref: #/definitions/Topic

$ref: #/definitions/ReliableTopic

$ref: #/definitions/Ringbuffer

$ref: #/definitions/FlakeIdGenerator

$ref: #/definitions/Listeners

$ref: #/definitions/Serialization

$ref: #/definitions/NativeMemory

$ref: #/definitions/Security

$ref: #/definitions/MemberAttributes

$ref: #/definitions/SplitBrainProtection

$ref: #/definitions/LiteMember

$ref: #/definitions/HotRestartPersistence

$ref: #/definitions/Persistence

$ref: #/definitions/UserCodeDeployment

$ref: #/definitions/CrdtReplication

$ref: #/definitions/PNCounter

$ref: #/definitions/AdvancedNetwork

$ref: #/definitions/CPSubsystem

$ref: #/definitions/Metrics

$ref: #/definitions/Sql

$ref: #/definitions/Auditlog

$ref: #/definitions/InstanceTracking

$ref: #/definitions/Jet

$ref: #/definitions/LocalDevice

$ref: #/definitions/DynamicConfiguration

$ref: #/definitions/IntegrityChecker

$ref: #/definitions/DataConnectionConfig

$ref: #/definitions/TpcConfig

description: Specifies the cluster name. It's sent as part of the client authentication message to Hazelcast member(s).

description: The 'client-labels' sequence lets you define labels in your Java client, similar to the way it can be done for the members. Through the client labels, you can assign special roles for your clients and use these roles to perform some actions specific to those client connections. You can also group your clients using the client labels. These client groups can be blacklisted in the Hazelcast Management Center so that they can be prevented from connecting to a cluster. See the related section in the Hazelcast Management Center Reference Manual for more information on this topic.

description: The 'backup-ack-to-client-enabled' element lets you enable/disable backups ack to client. This feature reduces number of hops and increase performance for smart clients. It is enabled by default for smart clients. This config has no effect for unisocket clients.

$ref: #/definitions/ProxyFactories

$ref: #/definitions/LoadBalancer

$ref: #/definitions/ClientNearCache

$ref: #/definitions/ClientFlakeIdGenerator

$ref: #/definitions/ClientReliableTopic

$ref: #/definitions/ClientUserCodeDeployment

$ref: #/definitions/ClientMetrics

$ref: #/definitions/ConnectionStrategy

$ref: #/definitions/ClientSecurity

$ref: #/definitions/ClientNetwork

$ref: #/definitions/ClientSql

$ref: #/definitions/ClientTpc

description: The Hazelcast client can configurations that the client is using to connect to a Hazelcast cluster in the case of a disconnect is listed under the "clients" array. You can list client configurations as many as you want.

description: Set to true to allow scripting on the member, false to disallow.

description: Set to true to allow console commands execution on the member, false to disallow.

description: Set to true to allow Management Center access to contents of Hazelcast data structures (for instance map entries), false to disallow. Management Center can't access the data if at least one member has the data access disabled.

description: This configuration lets you choose a discovery mechanism that Hazelcast will use to form a cluster. Hazelcast can find members by multicast, TCP/IP lists and by various discovery mechanisms provided by different cloud APIs.

description: Set its "enabled" attribute to true for discovery by multicast. It has another attribute ("loopback-mode-enabled") which enables or disables the loopback mode in the multicast discovery mechanism.

description: Specifies whether multicast discovery is enabled.

description: Specifies if the loopback mode is enabled for multicast discovery.

description: Alias for loopback-mode-enabled

description: Specifies the multicast group IP address when you want to create clusters within the same network.

description: Specifies the multicast socket port that the Hazelcast member listens to and sends discovery messages through.

description: Time-to-live value for multicast packets sent out to control the scope of multicasts.

description: Only when the members are starting up, this timeout (in seconds) specifies the period during which a member waits for a multicast response from another node. For example, if you set it as 60 seconds, each node will wait for 60 seconds until a leader node is selected.

description: Includes IP addresses of trusted members. When a node wants to join to the cluster, its join request will be rejected if it is not a trusted member. You can give an IP addresses range using the wildcard (*) on the last digit of IP address (e.g. 192.168.1.* or 192.168.1.100-110).

description: Specifies whether the TCP/IP discovery is enabled or not.

description: The maximum amount of time Hazelcast is going to try to connect to a well known member before giving up. Setting it to a too low value could mean that a member is not able to connect to a cluster. Setting it to a too high value means that member startup could slow down because of longer timeouts (e.g. when a well known member is not up). Increasing this value is recommended if you have many IPs listed and the members cannot properly build up the cluster.

description: IP address of the required member. Cluster will only be formed if the member with this IP address is found.

description: IP address(es) of one or more well known members. Once members are connected to these well known ones, all member addresses will be communicated with each other. You can also give comma separated IP addresses using the "members" element or list the members with the "member" element under "member-list".

description: Comma separated IP addresses of one or more well known members.

description: Sequence of IP address(es) of one or more well known members.

description: IP address(es) of one or more well known members.

description: IMPORTANT\nThis configuration is not intended to provide addresses of other cluster members with which the Hazelcast instance will form a cluster. This is an SPI for advanced use in cases where the DefaultAddressPicker does not pick suitable addresses to bind to and publish to other cluster members. For instance, this could allow easier deployment in some cases when running on Docker, AWS or other cloud environments. That said, if you are just starting with Hazelcast, you will probably want to set the member addresses by using the tcp-ip or multicast configuration or adding a discovery strategy. Member address provider allows to plug in own strategy to customize:\n1. What address Hazelcast will bind to\n2. What address Hazelcast will advertise to other members on which they can bind to\nIn most environments you don't need to customize this and the default strategy will work just fine. However in some cloud environments the default strategy does not make the right choice and the member address provider delegates the process of address picking to external code.

description: Specifies whether the member address provider SPI is enabled or not.

description: The name of the class implementing the com.hazelcast.spi.MemberAddressProvider interface.

description: The properties that will be provided when constructing the provided MemberAddressProvider. Hazelcast will first try instantiating the provided class by invoking a constructor accepting a single java.util.Properties instance. In the case where there is no such constructor and there are also no properties defined by this configuration, Hazelcast will exceptionally try to use the no-arg constructor.

description: You need to set it to true to be able to use your defined interfaces.

description: You can define multiple interfaces. By default, it is disabled.

description: A failure detector is responsible to determine if a member in the cluster is unreachable or crashed. Please refer to https://docs.hazelcast.org/docs/latest/manual/html-single/index.html#failure-detector-configuration for the failure detectors implemented by Hazelcast.

description: ICMP can be used in addition to the other detectors. It operates at layer 3 and detects network and hardware issues more quickly.

description: Timeout in milliseconds before declaring a failed ping.

description: Cluster Member will fail to start if it is unable to action an ICMP ping command when ICMP is enabled. Failure is usually due to OS level restrictions.

description: Time in milliseconds between each ICMP ping.

description: Maximum number of consecutive failed attempts before declaring a member suspect.

description: Run ICMP detection in parallel with the Heartbeat failure detector.

description: Maximum number of times the IP Datagram (ping) can be forwarded, in most cases all Hazelcast cluster members would be within one network switch/router therefore default of 0 is usually sufficient.

description: Please refer to https://github.com/hazelcast/hazelcast-aws/#configuration for the configuration details.

description: Specifies whether AWS discovery is enabled or not.

description: Please refer to https://github.com/hazelcast/hazelcast-gcp/#configuration for the configuration details.

description: Specifies whether Google Cloud Platform discovery is enabled or not.

description: Please refer to https://github.com/hazelcast/hazelcast-azure/#configuring-at-hazelcast-side for the configuration details.

description: Specifies whether Microsoft Azure discovery is enabled or not.

description: Please refer to https://github.com/hazelcast/hazelcast-eureka#hazelcast-configuration for the configuration details.

description: Specifies whether Eureka Service Registry discovery is enabled or not.

description: Set its "enabled" sub-element to true for discovery in various cloud infrastructures. You also need to set the value of "hazelcast.discovery.enabled" property to true. See the description of the "properties" element to learn how to do this. You can define multiple discovery strategies using the "discovery-strategy" sub-element and its properties. Please refer to http://docs.hazelcast.org/docs/latest/manual/html-single/index.html#discovering-cluster-members to see the properties you can use.

description: Overrides the public address of a node. By default, a node selects its socket address as its public address. But behind a network address translation (NAT), two endpoints (nodes) may not be able to see/access each other. If both nodes set their public addresses to their defined addresses on NAT, then they can communicate with each other. In this case, their public addresses are not an address of a local network interface but a virtual address defined by NAT. This is optional to set and useful when you have a private cloud.

description: When you shutdown a cluster member, the server socket port will be in the TIME_WAIT state for the next couple of minutes. If you start the member right after shutting it down, you may not be able to bind it to the same port because it is in the TIME_WAIT state. If you set reuse-address to true, the TIME_WAIT state is ignored and you can bind the member to the same port again.

description: Specifies the ports that Hazelcast will use to communicate between cluster members.

description: By default, Hazelcast will try 100 ports to bind (i.e. the ports between 5701 and 5801). You can change the port count in such cases as having large instances on a single machine or you are willing to have only a few ports assigned.

description: By default, Hazelcast tries to find a port by automatically incrementing the port numbers. If you don't want this (for example, you want to use a specific port), set auto-increment to false. If it is set to false, the port-count attribute is ignored.

description: Allows to configure Memcache text protocol support in Hazelcast.

description: Lets you encrypt the entire socket level communication among all Hazelcast members. This feature is available only in Hazelcast Enterprise.  Its configuration contains the encryption properties and the same configuration must be placed to all members. By default, it is disabled.

description: Indicates whether the advanced network configuration is enabled or not.

description: Configures the server sockets used for the WAN replication's inbound WAN connections. Multiple WAN server sockets can be configured to allow configuring separate server sockets for each inbound WAN connection.

description: Configures the server socket used for the member-client communication.

description: Configures the server socket used for the member-member communication.

description: This element configures socket settings for the outgoing WAN connections.

description: Controls access to Hazelcast HTTP REST API. The methods available through REST API are grouped to several REST endpoint groups, which can be specified in this section.

enum: endpoint-groups port public-address reuse-address name outbound-ports interfaces ssl socket-interceptor symmetric-encryption socket-options tpc-socket

examples: ExpirationTimeMergePolicy HyperLogLogMergePolicy HigherHitsMergePolicy PutIfAbsentMergePolicy DiscardMergePolicy LatestUpdateMergePolicy PassThroughMergePolicy LatestAccessMergePolicy

description: Adds the Split Brain Protection for this data-structure which you configure using the "split-brain-protection" element. You should set the "split-brain-protection-ref"'s value as the "split-brain-protection"'s name.

description: Binary type that will be used for storing records. Possible values: BINARY (default): keys and values will be stored as binary data. OBJECT: values will be stored in their object forms. NATIVE: values will be stored in non-heap region of JVM (Hazelcast Enterprise only)

description: Defines an assortment of transformations which can be applied to unique-key values. OBJECT: Extracted unique key value is interpreted as an object value. Non-negative unique ID is assigned to every distinct object value. LONG: Extracted unique key value is interpreted as a whole integer value of byte, short, int or long type. The extracted value is upcasted to long (if necessary) and unique non-negative ID is assigned to every distinct value. RAW: Extracted unique key value is interpreted as a whole integer value of byte, short, int or long type. The extracted value is upcasted to long (if necessary) and the resulting value is used directly as an ID.

description: Page size of the index B+ Tree. Default value is 16 kB.

description: Memory tier.

description: Memory tier capacity, i.e., how much main memory should this tier consume at most. The default is 256 megabytes.

description: The maximum number of seconds for each entry to stay in the map.

description: Sets if read-backup-data (reading local backup entries) is enabled for this map.

description: Sets whether hot restart is enabled on related data structure.

description: Sets whether disk write should be followed by an fsync() system call.

description: Sets whether persistence is enabled on related data structure.

description: The capacity is the total number of items that the event journal can hold at any moment. The actual number of items contained in the journal can be lower. NOTE: The capacity is shared equally between all partitions. This is done by assigning each partition {capacity / partitionCount} available slots in the event journal. Because of this, the effective total capacity may be somewhat lower and you must make sure that the configured capacity is at least greater than the partition count.

description: Time to live is the time the event journal retains items before removing them from the journal. The events are removed on journal read and write actions, not while the journal is idle. Time to live can be disabled by setting timeToLiveSeconds to 0. This means that the events never expire but they can be overwritten when the capacity of the journal is exceeded.

description: LAZY: Default load mode where load is async; EAGER: load mode where load is blocked till all partitions are loaded.

description: Set true to offload map-store interacting code parts from partition threads, otherwise interaction is executed inside partition thread

description: The number of seconds to delay before writing (storing) the dirty records.

description: The number of operations to be included in each batch processing round.

description: Setting writeCoalescing is meaningful if you are using write-behind MapStore. When writeCoalescing is true, only the latest store operation on a key in the writeDelaySeconds time-window will be reflected to MapStore.

description: The name for the MapStore implementation class

description: The name for the MapStoreFactory implementation class

description: The maximum number of seconds for each entry to stay in the Near Cache (time to live). Entries that are older than timeToLiveSeconds will automatically be evicted from the Near Cache.

description: The maximum number of seconds each entry can stay in the Near Cache as untouched (not-read). Entries that are not read (touched) more than maxIdleSeconds value will get removed from the Near Cache. Accepts any integer between 0 and Integer#MAX_VALUE. The value 0 means Integer#MAX_VALUE. The default is 0.

description: Sets if Near Cache entries are invalidated when the entries in the backing data structure are changed. When this setting is enabled, a Hazelcast instance with a Near Cache listens for cluster-wide changes on the entries of the backing data structure and invalidates its corresponding Near Cache entries. Changes done on the local Hazelcast instance always invalidate the Near Cache immediately.

description: Sets if local entries are also cached in the Near Cache. This is useful when the in-memory format of the Near Cache is different from the backing data structure. This setting has no meaning on Hazelcast clients, since they have no local entries.

description: Defines how to reflect local updates to the Near Cache. Possible values:\n * INVALIDATE: Local put and local remove immediately invalidate Near Cache.\n * CACHE_ON_UPDATE: While local remove immediately invalidates Near Cache, local put adds new value to it.

description: Sets if incoming WAN events to this member should be republished (forwarded) to this WAN replication reference.

description: Array of class names implementing the CacheWanEventFilter or MapWanEventFilter for filtering outbound WAN replication events. NOTE: EE only

description: Fully qualified class name of the extractor used to extract the value of the attribute.

description: Contains the configuration of a custom attribute that will be extracted from a Map's entry using a given ValueExtractor.

description: Adds listeners (listener classes) for the map entries using the "entry-listener" sub-elements

description: In client configurations it is used to identify the map to which this query cache belongs to.

description: Enables value caching.

description: Predicate to filter events which will be applied to the query cache.

description: Flag to enable/disable initial population of the QueryCache.

description: Defines if the Query Cache keys should be serialized or not. Keys are better to be serialized if they are mutable and need to be cloned via serialization. Default value is false.

description: Minimum time in seconds that an event waits in the member's buffer.

description: The batch size which will be used to determine number of events to be sent in a batch to QueryCache.

description: Maximum number of events which can be stored in a buffer of partition.

description: True if Tiered-Store is enabled, false otherwise.

description: Memory tier.

description: Disk tier.

description: True to enable using disk as the second memory tier, false otherwise.

description: Name of the device for a given disk tier.

description: List of key attributes to use for partitioning the data in the maps. Providing this list automatically sets the strategy to `com.hazelcast.partition.strategy.AttributePartitioningStrategy` regardless of the class name provided in the `partition-strategy` property.

description: True if you want the entry event to contain the item values.

description: True if you want to listen to the entries on the local member.

description: Maximum size of the set (item count). Its default value is 0, meaning Integer.MAX_VALUE.

description: True if statistics gathering is enabled on the set, false otherwise.

description: When it is set to true, all cluster members that listen to a topic will receive the messages in the same order they were published by all members. This way, Hazelcast guarantees that all members will see the in the same order. Its default value is false.

description: When you enable it, you can retrieve topic statistics such as total number of published and received messages. Its default value is true.

description: Enable multi-threaded message handling. When enabled any thread from events thread pool can be used for incoming message processing. Otherwise only one dedicated thread will be used to handle topic messages. Note: it can be enabled only in case when global ordering is disabled. Moreover, the local message ordering is not supported in this mode also. This means the messages produced by local publisher can be processed by several threads with no ordering guarantee.

description: Enables or disables statistics for this reliable topic. Collects the creation time, total number of published and received messages for each member locally.

description: A policy to deal with an overloaded topic; so topic where there is no place to store new messages. This policy can only be used in combination with the com.hazelcast.core.HazelcastInstance#getReliableTopic(String). The reliable topic uses a com.hazelcast.ringbuffer.Ringbuffer to store the messages. A ringbuffer doesn't track where readers are, so it has no concept of a slow consumers. This provides many advantages like high performance reads, but it also gives the ability to the reader to re-read the same message multiple times in case of an error. A ringbuffer has a limited, fixed capacity. A fast producer may overwrite old messages that are still being read by a slow consumer. To prevent this, we may configure a time-to-live on the ringbuffer (see com.hazelcast.config.RingbufferConfig#setTimeToLiveSeconds(int). Once the time-to-live is configured, the TopicOverloadPolicy controls how the publisher is going to deal with the situation that a ringbuffer is full and the oldest item in the ringbuffer is not old enough to get overwritten. Keep in mind that this retention period (time-to-live) can keep messages from being overwritten, even though all readers might have already completed reading. Its default value is BLOCK. Available values are as follows: - DISCARD_OLDEST: Using this policy, a message that has not expired can be overwritten. No matter the retention period set, the overwrite will just overwrite the item. This can be a problem for slow consumers because they were promised a certain time window to process messages. But it will benefit producers and fast consumers since they are able to continue. This policy sacrifices the slow producer in favor of fast producers/consumers. - DISCARD_NEWEST: Message that was to be published is discarded. - BLOCK: The caller will wait until there is space in the Ringbuffer. - ERROR: The publish call fails immediately.

description: Sets the read batch size. The ReliableTopic tries to read a batch of messages from the ringbuffer. It will get at least one, but if there are more available, then it will try to get more to increase throughput. The maximum read batch size can be influenced using the read batch size. Apart from influencing the number of messages to retrieve, the readBatchSize also determines how many messages will be processed by the thread running the MessageListener before it returns back to the pool to look for other MessageListeners that need to be processed. The problem with returning to the pool and looking for new work is that interacting with an executor is quite expensive due to contention on the work-queue. The more work that can be done without retuning to the pool, the smaller the overhead. If the readBatchSize is 10 and there are 50 messages available, 10 items are retrieved and processed consecutively before the thread goes back to the pool and helps out with the processing of other messages. If the readBatchSize is 10 and there are 2 items available, 2 items are retrieved and processed consecutively. If the readBatchSize is an issue because a thread will be busy too long with processing a single MessageListener and it can't help out other MessageListeners, increase the size of the threadpool so the other MessageListeners don't need to wait for a thread, but can be processed in parallel.

description: Number of items in the Ringbuffer. If no "time-to-live-seconds" is set, this value will always be equal to the capacity after the head completes the first loop around the ring. This is because no items are being expired.

description: Sets the time to live in seconds which is the maximum number of seconds for each item to stay in the ringbuffer before being removed. Entries that are older than time-to-live-seconds are removed from the ringbuffer on the next ringbuffer operation (read or write). Time to live can be disabled by setting time-to-live-seconds to 0. It means that items won't get removed because they expire. They may only be overwritten. When time-to-live-seconds is disabled and after the tail does a full loop in the ring, the ringbuffer size will always be equal to the capacity. The time-to-live-seconds can be any integer between 0 and Integer#MAX_VALUE. 0 means infinite. The default is 0.

description: Sets the in-memory format. Setting the in-memory format controls the format of the stored item in the ringbuffer: - OBJECT: the item is stored in deserialized format (a regular object) - BINARY (default): the item is stored in serialized format (a binary blob) The object in-memory format is useful when: - the object stored in object format has a smaller footprint than in binary format - if there are readers using a filter. Since for every filter invocation, the object needs to be available in object format.

description: Fully qualified class name.

description: Fully qualified name of the RingbufferStoreFactory implementation class.

description: Sets how many IDs are pre-fetched on the background when one call to FlakeIdGenerator.newId() is made. Value must be in the range 1..100,000. This setting pertains only to newId() calls made on the member that configured it.

description: Sets for how long the pre-fetched IDs can be used. If this time elapses, a new batch of IDs will be fetched. Time unit is milliseconds, default is 10 minutes. The IDs contain timestamp component, which ensures rough global ordering of IDs. If an ID is assigned to an object that was created much later, it will be much out of order. If you don't care about ordering, set this value to 0. This setting pertains only to newId() calls made on the member that configured it.

description: Sets the offset of timestamp component. Time unit is milliseconds, default is 1.1.2018 0:00 UTC. If you set the epoch start to a future instant, negative IDs will be generated until that time occurs.

description: Sets the offset that will be added to the node ID assigned to cluster member for this generator. Might be useful in A/B deployment scenarios where you have cluster A which you want to upgrade. You create cluster B and for some time both will generate IDs and you want to have them unique. In this case, configure node ID offset for generators on cluster B.

description: Sets the bit-length of the sequence component

description: Sets the bit-length of node id component.

description: Sets how far to the future is the generator allowed to go to generate IDs without blocking.

description: When you enable it, you can retrieve the Flake ID generators statistics.

description: When you enable it, you can retrieve queue statistics.

description: Maximum size of the queue. When a JVM's local queue size reaches the maximum, all put/offer operations will be blocked until the queue size of the JVM goes below this maximum. Its default value is 0, meaning Integer.MAX_VALUE

description: Used to purge unused or empty queues. If you define a value (time in seconds) for this element, then your queue will be destroyed if it stays empty or unused for that time.

description: Includes configuration elements and attributes for your queue store implementation. When you want to load/store the distributed queue items from/to a persistent datastore, first implement Hazelcast's QueueStore interface and then configure it using this element

description: The fully qualified name of the QueueStore implementation you want to use

description: The fully qualified name of the QueueStoreFactory which will be created by Hazelcast to instantiate QueueStores.

description: If you do not reach the queue store from an external application, you might prefer to insert the items in binary form. To do so, set this property to true and skip the deserialization step, which is a performance optimization.

description: Number of items after which Hazelcast will store items only to datastore. For example, if the memory limit is 1000, then the 1001st item will be put only to datastore. This feature is useful when you want to avoid out-of-memory conditions. If you want to always use memory, you can set it to Integer.MAX_VALUE.

description: Size of the bulks loaded from QueueStore when the queue is initialized.

description: Fully-qualified comparator's class name to be used for the priority queue. If nothing is provided, then queue behaves as a FIFO queue.

description: Set to true if you want the item event to contain the item values.

description: The in-memory format being used for representing the multimap. If it is false, the OBJECT in-memory format will be used.

description: Specifies whether the replicated map is available for reads before the initial replication is completed. If false, no Exception will be thrown when the replicated map is not yet ready, but call is blocked until the initial replication is completed.

description: When you enable it, you can retrieve replicated map entry statistics such as creation time, expiration time, number of hits, key, value, etc.

description: When you enable it, you can retrieve cache entry statistics such as creation time, expiration time, number of hits, key, value, etc.

description: If set to true, JMX beans are enabled and collected statistics are provided. It doesn't automatically enable statistics collection.

description: If set to true, enables read-through behavior of the cache to an underlying configured javax.cache.integration.CacheLoader which is also known as lazy-loading.

description: If set to true, enables write-through behavior of the cache to an underlying configured javax.cache.integration.CacheWriter which passes any changed value to the external backend resource.

description: Fully qualified class name of the javax.cache.configuration.Factory implementation providing a javax.cache.integration.CacheLoader instance to the cache.

description: Name of the cache loader class.

description: Fully qualified class name of the javax.cache.configuration.Factory implementation providing a javax.cache.integration.CacheWriter instance to the cache.

description: Name of the cache writer class.

description: Fully qualified class name of the javax.cache.configuration.Factory implementation providing a javax.cache.expiry.ExpiryPolicy instance to the cache.

enum: CREATED MODIFIED ACCESSED TOUCHED ETERNAL

enum: NANOSECONDS MICROSECONDS MILLISECONDS SECONDS MINUTES HOURS DAYS

description: If set to true, previously assigned values for the affected keys will be sent to the javax.cache.event.CacheEntryListener implementation. Setting this attribute to true creates additional traffic.

description: If set to true, the javax.cache.event.CacheEntryListener implementation will be called in a synchronous manner.

description: Fully qualified class name of the javax.cache.configuration.Factory implementation providing a javax.cache.event.CacheEntryListener instance.

description: Fully qualified class name of the javax.cache.configuration.Factory implementation providing a javax.cache.event.CacheEntryEventFilter instance.

description: List of cache entry listeners.

description: Name of the WAN replication configuration

description: When enabled, an incoming event to a member is forwarded to target cluster of that member.

description: Filters to intercept WAN replication events before they are placed to WAN event replication queues by providing a filtering API. Just implement Hazelcast's CacheWanEventFilter interface to create your filters.

description: Resolve conflicts that occurred when target cluster already has the replicated entry key.

description: Adds the split brain protection for this cache. The value should be a "split-brain-protection"'s name.

description: Adds the partition lost listeners that you created by implementing Hazelcast's PartitionLostListener interface.

description: Used to enable Hazelcast's Hot Restart Persistence feature for the cache. It is available only in Hazelcast Enterprise HD. Set its "enabled" to true to enable the feature. By default, it is disabled.

description: Set as true if the writing to disk should be followed by an fsync() system call.

description: Used to enable Hazelcast's Persistence feature for the cache. It is available only in Hazelcast Enterprise HD. Set its "enabled" to true to enable the feature. By default, it is disabled.

description: The capacity of the event journal. The capacity is the total number of items that the event journal can hold at any moment. The actual number of items contained in the journal can be lower. The capacity is shared equally between all partitions. This is done by assigning each partition capacity / partitionCount available slots in the event journal. Because of this, the effective total capacity may be somewhat lower and you must take into account that the configured capacity is at least greater than the partition count.

description: Sets the time to live in seconds. Time to live is the time the event journal retains items before removing them from the journal. The events are removed on journal read and write actions, not while the journal is idle. Time to live can be disabled by setting timeToLiveSeconds to 0. This means that the events never expire but they can be overwritten when the capacity of the journal is exceeed. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite.

description: Disables invalidation events for each entry; but full-flush invalidation events are still enabled. Full-flush invalidation means the invalidation of events for all entries when clear is called.

description: Fully qualified class name.

description: Fully qualified class name.

description: Defines the Hazelcast Management Center related metrics configuration.

description: Controls whether the metrics collected are exposed to Hazelcast Management Center. Please note that the metrics are polled by the Hazelcast Management Center, hence the members need to buffer the collected metrics between two polls. The aim for this switch is to reduce memory consumption of the metrics system if the Hazelcast Management Center is not used.

description: Sets the number of seconds the metrics will be retained on the instance. More retention means more heap memory, but allows for longer client hiccups without losing a value (for example to restart the Management Center).

enum: enabled management-center jmx collection-frequency-seconds

description: The master-switch for the metrics collection. If this is set to false no metrics collection is done, regardless of the other settings.

description: Defines the JMX related metrics configuration.

description: Controls whether the metrics collected are exposed to through JMX. It is enabled by default. In order to expose the metrics, the metrics system need to be enabled via the enabled master-switch attribute.

description: Sets the metrics collection frequency in seconds.

description: When you want to use a Hazelcast member as a lite member, set this element's "enabled" attribute to true in that member's YAML configuration. Lite members do not store data, do not have partitions and are used mainly to execute tasks and register listeners.

description: Number of CP Members to initialize the CP Subsystem. The CP subsystem is enabled when a positive value is set. After the CP subsystem is initialized successfully, more CP members can be added at run-time and number of active CP members can go beyond the configured CP member count. Number of CP members can be smaller than total size of the Hazelcast cluster. For instance, you can run 5 CP members in a 20-member Hazelcast cluster. If set, must be greater than or equal to "group-size".

description: Number of CP members to run CP groups. If set, it must be an odd number between 3 and 7. Otherwise, "cp-member-count" is respected. If set, must be smaller than or equal to "cp-member-count".

description: Duration for a CP session to be kept alive after the last received heartbeat. The session will be closed if there is no new heartbeat this duration. Session TTL must be decided wisely. If a very low value is set, CP session of a Hazelcast instance can be closed prematurely if the instance temporarily loses connectivity to the CP subsystem because of a network partition or a GC pause. In such an occasion, all CP resources of this Hazelcast instance, such as FencedLock or ISemaphore, are released. On the other hand, if a very large value is set, CP resources can remain assigned to an actually crashed Hazelcast instance for too long and liveliness problems can occur. The CP subsystem offers an API, CPSessionManagementService, to deal with liveliness issues related to CP sessions. In order to prevent premature session expires, session TTL configuration can be set a relatively large value and CPSessionManagementService#forceCloseSession() can be manually called to close CP session of a crashed Hazelcast instance. Must be greater than "session-heartbeat-interval-seconds", and smaller than or equal to "missing-cp-member-auto-removal-seconds".

description: Interval for the periodically-committed CP session heartbeats. A CP session is started on a CP group with the first session-based request of a Hazelcast instance. After that moment, heartbeats are periodically committed to the CP group. Must be smaller than "session-time-to-live-seconds".

description: Duration to wait before automatically removing a missing CP member from the CP subsystem. When a CP member leaves the cluster, it is not automatically removed from the CP subsystem, since it could be still alive and left the cluster because of a network partition. On the other hand, if a missing CP member is actually crashed, it creates a danger for its CP groups, because it will be still part of majority calculations. This situation could lead to losing majority of CP groups if multiple CP members leave the cluster over time. With the default configuration, missing CP members will be automatically removed from the CP subsystem after 4 hours. This feature is very useful in terms of fault tolerance when CP member count is also configured to be larger than group size. In this case, a missing CP member will be safely replaced in its CP groups with other available CP members in the CP subsystem. This configuration also implies that no network partition is expected to be longer than the configured duration. Must be greater than or equal to "session-time-to-live-seconds". If a missing CP member comes back alive after it is automatically removed from the CP subsystem with this feature, that CP member must be terminated manually. The default is 4 hours.

description: Offers a choice between at-least-once and at-most-once execution of the operations on top of the Raft consensus algorithm. It is disabled by default and offers at-least-once execution guarantee. If enabled, it switches to at-most-once execution guarantee. When you invoke an API method on a CP data structure proxy, it replicates an internal operation to the corresponding CP group. After this operation is committed to majority of this CP group by the Raft leader node, it sends a response for the public API call. If a failure causes loss of the response, then the calling side cannot determine if the operation is committed on the CP group or not. In this case, if this configuration is disabled, the operation is replicated again to the CP group, and hence could be committed multiple times. If it is enabled, the public API call fails with com.hazelcast.core.IndeterminateOperationStateException

description: Flag to denote whether or not CP Subsystem Persistence is enabled. If enabled, CP members persist their local CP data to stable storage and can recover from crashes.

description: Base directory to store all CP data when persistence-enabled is true. This directory can be shared between multiple CP members. Each CP member creates a unique directory for itself under the base directory. This is especially useful for cloud environments where CP members generally use a shared filesystem.

description: Timeout duration for CP members to restore their data from disk. CP member fails its startup if it cannot complete its CP data restore rocess in the configured duration.

description: The CP member priority. The CP groups' leadership will be eventually transferred to members with higher priorities within the CP group.

description: Leader election timeout in milliseconds. If a candidate cannot win majority of the votes in time, a new election round is initiated.

description: Period in milliseconds for a leader to send heartbeat messages to its followers.

description: Maximum number of missed leader heartbeats to trigger a new leader election.

description: Maximum number of entries that can be sent in a single batch of append entries request.

description: Number of new commits to initiate a new snapshot after the last snapshot.

description: Maximum number of uncommitted entries in the leader's Raft log before temporarily rejecting new requests of callers.

description: Timeout in milliseconds for append request backoff. After the leader sends an append request to a follower, it will not send a subsequent append request until the follower responds to the former request or this timeout occurs.

description: Enables / disables JDK compatibility of the CP ISemaphore. When it is JDK compatible, just as in the Semaphore#release() method, a permit can be released without acquiring it first, because acquired permits are not bound to threads. However, there is no auto-cleanup of acquired permits upon Hazelcast server / client failures. If a permit holder fails, its permits must be released manually. When JDK compatibility is disabled, a HazelcastInstance must acquire permits before releasing them and it cannot release a permit that it has mot acquired. It means, you can acquire a permit from one thread and release it from another thread using the same HazelcastInstance, but not different HazelcastInstances. In this mode, acquired permits are automatically released upon failure of the holder HazelcastInstance. So there is a minor behavioral difference to the Semaphore#release() method.

description: Number of permits to initialize the Semaphore. If a positive value is set, the Semaphore is initialized with the given number of permits.

description: Configurations for CP Semaphore instances. The CP Semaphores can be configured with mappings under keys as their names.

description: Configurations for FencedLock instances. The FencedLocks can be configured with mappings under keys as their names.

description: Maximum number of reentrant lock acquires. Once a caller acquires the lock this many times, it will not be able to acquire the lock again, until it makes at least one unlock() call. By default, no upper bound is set for the number of reentrant lock acquires, which means that once a caller acquires a FencedLock, all of its further lock() calls will succeed. However, for instance, if you set lock-acquire-limit to 2, once a caller acquires the lock, it will be able to acquire it once more, but its third lock() call will not succeed. If lock-acquire-limit is set to 1, then the lock becomes non-reentrant.

description: Number of synchronous backups. For example, if 1 is set as the backup count, then all entries of the map will be copied to another JVM for fail-safety. 0 means no sync backup. The sum of backup-count and async-backup-count can't be larger than than 6.

description: The number of asynchronous backups. 0 means no backups. The sum of backup-count and async-backup-count can't be larger than than 6.

description: Name-value pairs of list configurations

description: When you enable it, you can retrieve list statistics.

description: Maximum size of the list (item count). 0 means Integer.MAX_VALUE.

description: Adds the Split Brain Protection for this data-structure. You should set this value as a "split-brain-protection"'s name.

description: Set to true to enable Hazelcast's security features.

description: Defines set of named security realms. Security realms are named security configurations which can be referenced from Hazelcast security configuration. Currently, the realms support configuring "authentication", and/or "identity". Only one type of authentication configuration and one type of identity configuration is allowed per the realm.

description: Defines JAAS authentication - i.e. list of login-module descriptions and optional "properties"

description: TLS defines X.509 based authentication (for cases when SSL mutual authentication is configured in Hazelcast network configuration)

enum: username-password kerberos token credentials-factory

description: Maps member authentication to a realm name.

description: Maps client authentication to a realm name.

description: Specifies the name and properties of your class that you developed by implementing Hazelcast's IPermissionPolicy interface, which is the default permission policy (com.hazelcast.security.IPermissionPolicy). This policy defines the client authorization specifications.

description: Specifies the security interceptor class that you developed by implementing Hazelcast's SecurityInterceptor interface to intercept every remote operation executed by a client.

description: Specifies whether to block (true) or allow (false) actions, submitted as tasks in an Executor from the clients and have no permission mappings.

description: Lists the client permissions that can be accessed by the client permission policy. For each permission, you need to provide the end points and actions to be permitted. Also, the name and principal for each permission should be given using the "name" and "principal" attributes. Please see http://docs.hazelcast.org/docs/latest/manual/html-single/index.html#permissions for all permissions and actions.

enum: on-join-operation all config transaction map queue topic multimap list set flake-id-generator lock atomic-long countdown-latch semaphore executor-service durable-executor-service cardinality-estimator scheduled-executor cache user-code-deployment pn-counter atomic-reference ring-buffer reliable-topic replicatedmap management job connector sql

enum: all create destroy modify read remove lock listen release acquire put add index intercept publish aggregate projection deploy submit cancel restart export-snapshot add-resources write instance member migration create-view drop-view create-type drop-type view-dataconnection create-dataconnection drop-dataconnection

description: Unit can be bytes, kilobytes, megabytes and gigabytes. Default unit is MEGABYTES.

description: Default value is 128.

description: This feature is available only in Hazelcast Enterprise HD.

description: Set as true to enable the High-Density Memory Store usage.

description: Type of the memory allocator. The default value is POOLED. Available values are as follows: \n- STANDARD: Allocates/frees the memory using default OS memory manager, \n- POOLED: Manages memory blocks in thread local pools

description: Deprecated, use 'capacity' instead.

description: Minimum size of the blocks in bytes to split and fragment a page block to assign to an allocation request.\n It is used only by the POOLED memory allocator. The value has to be power of two. Default value is 16.

description: Size of the page in bytes to allocate memory as a block. \n It is used only by the POOLED memory allocator. Its default value is 1 << 22 (about 4 MB)

description: Percentage of the allocated native memory that is used for the metadata such as indexes, offsets, etc. \n It is used only by the POOLED memory allocator. Its default value is 12.5.

description: Specifies the directory where the non-volatile memory (e.g. Intel Optane) is mounted. \n If this element is not defined, the RAM is used as a native memory. \n This directory will be created automatically if it does not exist.\n To avoid collisions, every member of the cluster will create its own subfolder to work with the non-volatile memory.

description: Configures the replication mechanism for all CRDT implementations.\n The CRDT states are replicated in rounds (the period is configurable) and \n in each round the state is replicated up to the configured number of members

description: The maximum number of target members that we replicate the CRDT states to in one period. \n A higher count will lead to states being disseminated more rapidly at the expense of burst-like behaviour - \n one update to a CRDT will lead to a sudden burst in the number of replication messages in a short time interval.

description: The period between two replications of CRDT states in milliseconds. \n A lower value will increase the speed at which changes are disseminated to other cluster members at the expense of burst-like behaviour - \n less updates will be batched together in one replication message and \n one update to a CRDT may cause a sudden burst of replication messages in a short time interval. \n The value must be a positive non-null integer.

description: Number of replicas on which the CRDT state will be kept.

description: Adds the Split Brain Protection for this data-structure which you configure using the "split-brain-protection" element.

description: When you enable it, you can retrieve the PN counter statistics.

description: Configuration used to register the listeners that you created by implementing Hazelcast's MembershipListener, DistributedObjectListener, MigrationListener and PartitionLostListener interfaces.

description: You can define member attributes for your Hazelcast members to tag your members according to your business logic requirements. Configuration element's name is "member-attributes". You can list each member attribute by their name. For each attribute, you need to provide its type and value.

description: Version of the portable serialization. Portable version is used to differentiate two of the same classes that have changes such as a new field or a new field type.

description: Set as true if you want to use the native byte order of the underlying platform.

description: Specifies the byte order that the serialization will use.

description: Set as true to enable compression when default Java serialization is used. Its default value is false.

description: Set as true to enable shared object when default Java serialization is used.

description: Set as true to allow the usage of unsafe.

description: Lists your class implementations of Hazelcast's DataSerializableFactory. Each factory has the required

description: Lists your class implementations of Hazelcast's PortableFactory. Each factory has the required "factory-id" attribute that you should give as the ID of your factory.

description: Global serializer should be defined with "global-serializer" element. It has an optional boolean "override-java-serialization" attribute. If you set it as true, the Java serialization step will be handled by the global serializer, not by the Java Serializable or Externalizable

description: If you set it as true, the Java serialization step will be handled by the global serializer, not by the Java Serializable or Externalizable

description: Lists the serializers (classes) that you implement using Hazelcast's StreamSerializer, ByteArraySerializer etc.

description: The type of the class that will be serialized via this implementation.

description: The class name of the serializer implementation.

description: If set to true, serialization system will check the class definitions error at the start of serialization process and throw a Serialization Exception with the error definition.s

description: Allows to configure blacklisting and whitelisting for deserialized classes when Java serialization is used.

description: Contains configuration elements and attributes for the compact serialization.

description: Contains the Compact serializers to be registered.

description: Fully qualified class name of the Compact serializer.

description: Contains the classes to be serialized with Compact serialization, which will override any other serialization mechanisms.

description: Fully qualified name of the class.

description: Specifies whether this split brain protection is enabled.

description: The minimum number of members required in a cluster for the cluster to remain in an operational state. If the number of members is below the defined minimum at any time, the operations are rejected and the rejected operations return a SplitBrainProtectionException to their callers.

description: Specifies for which operations the split brain protection will be applied. Available values are READ, WRITE and READ_WRITE.

description: Name of the class that you develop by implementing Hazelcast's SplitBrainProtectionFunction interface to conclude the absence/presence of your split brain protection. This function is triggered when any change happens to the member list.

description: Provides the list of split brain protection listeners that you can register to be notified about split brain protection results. Split brain protection listeners are local to the member that they are registered, so they receive only events occurred on that local member.

description: Overrides the hazelcast.max.no.heartbeat.seconds system property.

description: Default duration in milliseconds corresponding to number of potentially lost/delayed heartbeats that will be accepted before considering it to be an anomaly. Overrides the hazelcast.max.no.heartbeat.seconds system property.

description: Threshold for suspicion (��) level. A low threshold is prone to generate many wrong suspicions but ensures a quick detection in the event of a real crash. Conversely, a high threshold generates fewer mistakes but needs more time to detect actual crashes. Overrides the hazelcast.heartbeat.phiaccrual.failuredetector.threshold system property.

description: Number of samples to use for calculations. Overrides the hazelcast.heartbeat.phiaccrual.failuredetector.sample.size system property.

description: Minimum standard deviation (in milliseconds) to use for the normal distribution used when calculating phi. Overrides the hazelcast.heartbeat.phiaccrual.failuredetector.min.std.dev.millis system propery.

description: Value of heartbeat interval in milliseconds. Overrides the hazelcast.heartbeat.interval.seconds system property.

description: Sets whether or not automatic removal of stale Hot Restart data is enabled. When a member terminates or crashes when cluster state is ACTIVE, remaining members redistributes data among themselves and data persisted on terminated member's storage becomes stale. That terminated member cannot rejoin the cluster without removing Hot Restart data. When auto-removal of stale Hot Restart data is enabled, while restarting that member, Hot Restart data is automatically removed and it joins the cluster as a completely new member. Otherwise, Hot Restart data should be removed manually.

description: Specifies the directory where the Hot Restart data will be stored. This directory will be created automatically if it does not exist.

description: Specifies the directory where the Hot backup data will be stored. If this element is not defined, hot backup will be disabled. If a directory is defined which does not exist, it will be created on first backup. To avoid clashing data on multiple backups, each backup has a unique sequence ID which determines the name of the directory which will contain all hot restart data. This unique directory is created as a subdirectory of the configured `backup-dir`.

description: Level of parallelism in Hot Restart Persistence. There will be this many IO threads, each writing in parallel to its own files. During the Hot Restart procedure, this many IO threads will be reading the files and this many Rebuilder threads will be rebuilding the Hot Restart metadata.

description: Validation timeout for the Hot Restart process when validating the cluster members expected to join and the partition table on the whole cluster.

description: Data load timeout for the Hot Restart process. All members in the cluster should finish restoring their local data before this timeout period.

description: Specifies the data recovery policy that will be respected during Hot Restart cluster start. Valid values are:\n FULL_RECOVERY_ONLY: Starts the cluster only when all expected members are present and correct. Otherwise, it fails. This is the default value.\n PARTIAL_RECOVERY_MOST_RECENT: Starts the cluster with the members which have most up-to-date partition table and successfully restored their data. All other members will leave the cluster and force start themselves. If no member restores its data successfully, cluster start fails.\n PARTIAL_RECOVERY_MOST_COMPLETE: Starts the cluster with the largest group of members which have the same partition table version and successfully restored their data. All other members will leave the cluster and force start themselves. If no member restores its data successfully, cluster start fails.

description: Specifies the (optional) encryption settings for Hot Restart persistence. It has the required attribute "enabled" to specify whether encryption is enabled. In addition to that, it specifies the symmetric cipher to use (such as AES/CBC/PKCS5Padding), the encryption salt, the key size for generating encryption keys and, in the "secure-store" sub-element, the configuration of the Secure Store that it will be used to retrieve the encryption keys.\n "keystore": Provides integration with Java KeyStore. Specifies the path to the KeyStore file, the KeyStore type (such as PKCS12 or JCEKS), the KeyStore password, an (optional) alias for the current encryption key entry, and (optionally) a polling interval for checking for changes in the KeyStore.\n "vault": Provides integration with HashiCorp Vault. Specifies the address of the Vault server, the (optional) secrets engine path, the secret path where the encryption key is stored, the access token, the (optional) namespace, the (optional) <ssl> configuration for HTTPS support, and an (optional) polling interval for checking for changes in Vault.

description: Symmetric encryption algorithm

description: Provides integration with Java KeyStore. Specifies the path to the KeyStore file, the KeyStore type (such as PKCS12 or JCEKS), the KeyStore password, an (optional) alias for the current encryption key entry, and (optionally) a polling interval for checking for changes in the KeyStore.

description: For information about standard keystore types see https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#KeyStore

description: The keystore password

description: Interval (in seconds) for polling for changes in the KeyStore. 0 (default) means no polling

description: Provides integration with HashiCorp Vault. Specifies the address of the Vault server, the (optional) secrets engine path, the secret path where the encryption key is stored, the access token, the (optional) namespace, the (optional) "ssl" configuration for HTTPS support, and an (optional) polling interval for checking for changes in Vault.

description: Interval (in seconds) for polling for changes to the encryption key. 0 (default) means polling disabled.

description: Specifies the directory where the Persistence data will be stored. This directory will be created automatically if it does not exist.

description: Specifies the directory where the Persistence backup data will be stored. If this element is not defined, backup will be disabled. If a directory is defined which does not exist, it will be created on first backup. To avoid clashing data on multiple backups, each backup has a unique sequence ID which determines the name of the directory which will contain all persistence data. This unique directory is created as a subdirectory of the configured `backup-dir`.

description: Level of parallelism in Persistence. There will be this many IO threads, each writing in parallel to its own files. During the restart procedure, this many IO threads will be reading the files and this many Rebuilder threads will be rebuilding the Persistence metadata.

description: Validation timeout for the restart process when validating the cluster members expected to join and the partition table on the whole cluster.

description: Data load timeout for the restart process. All members in the cluster should finish restoring their local data before this timeout period.

description: Specifies the data recovery policy that will be respected during restart cluster start. Valid values are:\n FULL_RECOVERY_ONLY: Starts the cluster only when all expected members are present and correct. Otherwise, it fails. This is the default value.\n PARTIAL_RECOVERY_MOST_RECENT: Starts the cluster with the members which have most up-to-date partition table and successfully restored their data. All other members will leave the cluster and force start themselves. If no member restores its data successfully, cluster start fails.\n PARTIAL_RECOVERY_MOST_COMPLETE: Starts the cluster with the largest group of members which have the same partition table version and successfully restored their data. All other members will leave the cluster and force start themselves. If no member restores its data successfully, cluster start fails.

description: Specifies the (optional) encryption settings for persistence. It has the required attribute "enabled" to specify whether encryption is enabled. In addition to that, it specifies the symmetric cipher to use (such as AES/CBC/PKCS5Padding), the encryption salt, the key size for generating encryption keys and, in the "secure-store" sub-element, the configuration of the Secure Store that it will be used to retrieve the encryption keys.\n "keystore": Provides integration with Java KeyStore. Specifies the path to the KeyStore file, the KeyStore type (such as PKCS12 or JCEKS), the KeyStore password, an (optional) alias for the current encryption key entry, and (optionally) a polling interval for checking for changes in the KeyStore.\n "vault": Provides integration with HashiCorp Vault. Specifies the address of the Vault server, the (optional) secrets engine path, the secret path where the encryption key is stored, the access token, the (optional) namespace, the (optional) <ssl> configuration for HTTPS support, and an (optional) polling interval for checking for changes in Vault.

description: Symmetric encryption algorithm

description: The keystore password

description: Time (in seconds) to wait before triggering automatic partition rebalancing after a member leaves the cluster unexpectedly. Unexpectedly in this context means that a member leaves the cluster by means other than graceful shutdown: programmatic termination (eg LifecycleService.terminate()), a process crash or network partition. Default is 0, which means rebalancing is triggered immediately. Setting this to a higher value will allow some time for members that are gone to rejoin the cluster. The benefit is that partition rebalancing in this case will be avoided, saving the burden of migrating partition data over the network. Do not use this option if your cluster also stores in-memory data. This option stops the cluster from migrating in-memory data. As a result any data that is not persisted will be lost if the member restarts within the configured delay, including backups. While members are gone, operations on partitions for which the owner is missing may fail immediately or will be retried until the member rejoins or operation timeout is exceeded. Notice that this delay only applies when cluster members leave the cluster; when the cluster is being scaled up and members are being added, partition rebalancing will be triggered immediately (subject to limitations imposed by the current cluster state).

description: Device base directory that will be used for tiered-store.

description: Device capacity, i.e., what is the soft upper bound capacity of the device. The default is 256 gigabytes.

description: Device block/sector size in bytes. The default is 4096. The minimum is 512.

description: Read IO thread count. The default is 4.

description: Write IO thread count. The default is 4.

description: True if dynamic configuration persistence is enabled.

description: Directory for dynamic configuration persistence file backups. Each new backup will be created inside this directory. Can be an absolute or relative path to the node startup directory. If not set, new folder will be created at the node startup directory.

description: How many backups will be kept. Default is 5. You can set this to zero to disable backups.

description: The ports which Hazelcast will use to communicate between cluster members.

description: The default value is 100, meaning that Hazelcast will try to bind 100 ports. If you set the value of port as 5701, as members join the cluster, Hazelcast tries to find ports between 5701 and 5801. You can change the port count in cases like having large instances on a single machine or you are willing to have only a few ports assigned.

description: If port is set to 5701, Hazelcast will try to find free ports between 5701 and 5801. Normally, you will not need to change this value, but it comes in handy when needed. You may also want to choose to use only one port. In that case, you can disable the auto-increment feature of port by setting its value as false.

description: Name of the endpoint configuration. Only relevant when defining WAN server sockets.

description: Specifies which network interfaces Hazelcast should use. You need to set its "enabled" sub-element to true to be able to use your defined interfaces. By default, it is disabled. You can define multiple interfaces using a nested "interfaces" sequence.

description: Lets you configure SSL using the SSL context factory. This feature is available only in Hazelcast Enterprise. To be able to use it, encryption should NOT be enabled and you should first implement your SSLContextFactory class. Its configuration contains the factory class and SSL properties.

description: Lets you add custom hooks to join and perform connection procedures (like identity checking using Kerberos, etc.). This feature is available only in Hazelcast Enterprise. To be able to use it, you should first implement the MemberSocketInterceptor (for members joining to a cluster) or SocketInterceptor (for clients connecting to a member) class. Its configuration contains the class you implemented and socket interceptor properties.

description: Lets you encrypt the entire socket level communication among all Hazelcast members. This feature is available only in Hazelcast Enterprise.  Its configuration contains the encryption properties and the same configuration must be placed to all members.

description: Specifies whether direct or non-direct buffers should be allocated for the socket.

description: Specifies whether Nagle's algorithm should be disabled. The default value is true meaning that Nagle's algorithm is disabled.

description: Specifies whether TCP keep-alive should be enabled.

description: Specifies the TCP timeout in seconds.

description: Specifies the size of the send buffer.

description: Specifies the size of the receive buffer.

description: Specifies the TCP linger seconds.

description: Specifies the TCP Keep-Alive idle time: the number of seconds of idle time before keep-alive initiates a probe. Valid values are 1 to 32767.

description: Specifies the TCP keep-alive interval: the number of seconds between keep-alive probes. Valid values are 1 to 32767.

description: Specifies the TCP Keep-Alive count: the maximum number of TCP keep-alive probes to send before giving up and closing the connection if no response is obtained from the other side. Valid values are 1 to 127.

description: Sets the cluster name used as an endpoint cluster name for authentication on the target endpoint. If there is no separate publisher ID property defined, this cluster name will also be used as a WAN publisher ID. This ID is then used for identifying the publisher in a WanReplicationConfig.

description: Changes the maximum size of events that are sent to the target cluster in a single batch. The batch of events is not sent until this size is reached.

description: If the number of events generated does not reach the "batch-size", they are sent to the target cluster after a certain amount of time is passed. You can set this time in milliseconds using this element.

description: After a replication event is sent to the target cluster, the source member waits for a confirmation that says the event has reached the target. If confirmation is not received for a period of `response-timeout-millis`, the event is resent to the target cluster.

description: Acknowledgment type for each target cluster when the events are replicated. You can set it to the following values: \n * ACK_ON_RECEIPT: Guarantees that events are received by the target cluster. It does not guarantee that the received event is actually applied, but it is faster. \n * ACK_ON_OPERATION_COMPLETE (default): Guarantees that the event is both received and applied by the target cluster. It is more time consuming, but it is the best way if you have strong consistency requirements.

description: Defines the initial state in which a WAN publisher is started. \n * REPLICATING (default): State where both enqueuing new events is allowed, enqueued events are replicated to the target cluster and WAN sync is enabled. \n * PAUSED: State where new events are enqueued but they not are dequeued. Some events which have been dequeued before the state was switched may still be replicated to the target cluster but further events will not be replicated. WAN sync is enabled. \n * STOPPED:  State where neither new events are enqueued nor dequeued. As with the PAUSED state, some events might still be replicated after the publisher has switched to this state. WAN sync is enabled.

description: Sets if key-based coalescing is configured for this WAN publisher. When enabled, only the latest WanReplicationEvent of a key is sent to target.

description: Sets the maximum duration in nanoseconds that the WAN replication thread will be parked if there are no events to replicate.

description: Sets the minimum duration in nanoseconds that the WAN replication thread will be parked if there are no events to replicate.

description: Sets the maximum number of WAN event batches being sent to the target cluster concurrently. Setting this property to anything less than 2 will only allow a single batch of events to be sent to each target endpoint and will maintain causality of events for a single partition. Setting this property to 2 or higher will allow multiple batches of WAN events to be sent to each target endpoint. Since this allows reordering or batches due to network conditions, causality and ordering of events for a single partition is lost and batches for a single partition are now sent randomly to any available target endpoint. This, however, does present faster WAN replication for certain scenarios such as replicating immutable, independent map entries which are only added once and where ordering of when these entries are added is not necessary. Keep in mind that if you set this property to a value which is less than the target endpoint count, you will lose performance as not all target endpoints will be used at any point in time to process WAN event batches. So, for instance, if you have a target cluster with 3 members (target endpoints) and you want to use this property, it makes sense to set it to a value higher than 3. Otherwise, you can simply disable it by setting it to less than 2 in which case WAN will use the default replication strategy and adapt to the target endpoint count while maintaining causality.

description: Sets the period in seconds in which WAN tries to discover new target endpoints and reestablish connections to failed endpoints.

description: Sets whether the WAN connection manager should connect to the endpoint on the private address returned by the discovery SPI. By default this property is false which means the WAN connection manager will always use the public address.

description: Policy to be applied when WAN Replication event queues are full. You can set it to the following values: \n - DISCARD_AFTER_MUTATION (default): The new WAN events generated are dropped and not replicated to the target cluster.

description: The maximum number of endpoints that WAN will connect to when using a discovery mechanism to define endpoints. This property has no effect when static endpoint addresses are defined using target-endpoints.

description: Size of the queue of events. If you exceed this queue size, then the oldest, not yet replicated updates might get lost. Therefore, if you have a large rate of put/update/remove operations, you should increase queue capacity.

description: Comma separated list of IP addresses of the target cluster members for which the WAN replication is implemented.

description: Sets the strategy for checking consistency of data between source and target cluster. Any inconsistency will not be reconciled, it will be merely reported via the usual mechanisms (e.g. statistics, diagnostics). The user must initiate WAN sync to reconcile there differences. For the check procedure to work properly, the target cluster should support the chosen strategy.

description: Config for processing WAN events received from a target cluster. You can configure certain behaviour when processing incoming WAN events or even configure your own implementation for a WAN consumer. A custom WAN consumer allows you to define custom processing logic and is usually used in combination with a custom WAN publisher. A custom consumer is optional and you may simply omit defining it which will cause the default processing logic to be used.

description: Sets the fully qualified class name of the class implementing a custom WAN consumer (WanConsumer). If you don't define a class name, the default processing logic for incoming WAN events will be used.

description: Properties for the custom WAN consumer. These properties are accessible when initalizing the WAN consumer.

description: When true, an incoming event over WAN replication can be persisted to a database for example, otherwise it will not be persisted. Default value is true.

description: Controls the local caching behavior for the classes loaded from the remote class repository. Available values are as follows:\n * ETERNAL: Cache the loaded classes locally. This is the default value and suitable when you load long-living objects, such as domain objects stored in a map. \n * OFF: Do not cache the loaded classes locally.

description: Controls how the classes are served to the other cluster members. Available values are as follows: \n * LOCAL_AND_CACHED_CLASSES: Serve classes loaded from both local classpath and from other members. This is the default value. \n * LOCAL_CLASSES_ONLY: Serve classes from the local classpath only. Classes loaded from other members will be used locally, but they are not served to other members. \n * OFF: Never serve classes to other members.

description: Comma separated name prefixes of classes/packages to be prevented from dynamic class loading. For example, if you set it as "com.foo", remote loading of all classes from the "com.foo" package will be blacklisted, including the classes from all its sub-packages. If you set it as "com.foo.Class", then the "Class" and all classes having the "Class" as prefix in the "com.foo" package will be blacklisted.

description: Comma separated name prefixes of classes/packages only from which the classes will be loaded. It allows to quickly configure remote loading only for classes from selected packages. It can be used together with blacklisting. For example, you can whitelist the prefix "com.foo" and blacklist the prefix "com.foo.secret".

description: Filter to constraint members to be used for a class loading request when a class is not available locally. The value is in the format "HAS_ATTRIBUTE:foo". When it is set as "HAS_ATTRIBUTE:foo", the class loading request will only be sent to the members which have "foo" as a member attribute.

description: Defines the timeout in milliseconds that is applied to queries without an explicit timeout.

description: Sets whether SQL Catalog persistence is enabled for the node. With SQL Catalog persistence enabled you can restart the whole cluster without losing schema definition objects (such as MAPPINGs, TYPEs, VIEWs and DATA CONNECTIONs). The feature is implemented on top of the Hot Restart feature of Hazelcast which persists the data to disk. If enabled, you have to also configure Hot Restart. Feature is disabled by default. If you enable this option in open-source, the member will fail to start, you need Enterprise to run it and obtain a license from Hazelcast.

description: The configuration when to retry query that fails with reasons CONNECTION_PROBLEM, PARTITION_DISTRIBUTION, TOPOLOGY_CHANGE.

description: Enables or disables the TPC-aware mode.

description: Configures the client for TPC, which is the next generation Hazelcast that uses thread-per-core model. TPC-aware clients will maintain connections to all cores of all cluster members. The client will route partition-specific invocations to the correct core of the correct member in the best effort basis. This configuration is introduced as BETA, and it might be subject to changes, or it can be removed in future releases without a prior notice.

description: By default, Hazelcast lets the system pick up an ephemeral port during socket bind operation. But security policies/firewalls may require you to restrict outbound ports to be used by Hazelcast-enabled applications. You can specify these ports under the element "outbound-ports". You can give a single port number, comma separated multiple ports or port ranges.

description: the number of threads each cluster member will use to execute Jet jobs. This refers only to threads executing `cooperative` processors; each `blocking` processor is assigned its own thread. By default it is the same as the number of available processors.

description: While executing a Jet job there is the issue of regulating the rate at which one member of the cluster sends data to another member. The receiver will regularly report to each sender how much more data it is allowed to send over a given DAG edge. This property sets the length (in milliseconds) of the interval between flow-control ("ack") packets.

description: Sets the number of backups that Jet will maintain for the job metadata and snapshots. Each backup is on another cluster member; all backup write operations must complete before the overall write operation can complete. The maximum allowed number of backups is 6 and the default is 1. For example, if you set the backup count to 2, Jet will replicate all the job metadata and snapshot data to two other members. If one or two members of the cluster fail, Jet can recover the data from the snapshot and continue executing the job on the remaining members without loss.

description: Sets the delay after which auto-scaled jobs will restart if a new member is added to the cluster. Has no effect on jobs with auto scaling disabled.

description: Sets whether lossless job restart is enabled for the node. With lossless restart you can restart the whole cluster without losing the jobs and their state. The feature is implemented on top of the Hot Restart feature of Hazelcast which persists the data to disk. If enabled, you have to also configure Hot Restart. Note: the snapshots exported using `Job#exportSnapshot` will also have Hot Restart storage enabled. Feature is disabled by default. If you enable this option in open-source, the member will fail to start, you need Enterprise to run it and obtain a license from Hazelcast.

description: Specifies the maximum number of records that can be accumulated by any single processor instance. Operations like grouping, sorting or joining require certain amount of records to be accumulated before they can proceed. You can set this option to reduce the probability of `OutOfMemoryError`. It applies to each processor instance separately, hence the effective limit of records accumulated by each cluster member is influenced by the vertex's `localParallelism` and the number of jobs in the cluster. Currently, this option limits: number of items sorted by the sort operation, number of distinct keys accumulated by aggregation operations, number of entries in each hash-join lookup table, number of entries in stateful transforms and number of distinct items in distinct operation. The limit does not apply to streaming aggregations.

description: Deprecated, use `/hazelcast/jet` to configure the fields directly. General configuration options pertaining to a Jet instance.

description: Sets the capacity of processor-to-processor concurrent queues. The value is rounded upwards to the next power of 2. When data needs to travel between two processors on the same cluster member, Jet sends it over a concurrent single-producer, single-consumer (SPSC) queue of fixed capacity. Since there are several processors executing the logic of each vertex, and since the queues are SPSC, there will be `senderParallelism input.txt receiverParallelism` queues representing the edge on each member. The edge capacity should strike a balance between performance and memory usage.

description: For a distributed edge, data is sent to a remote member via Hazelcast network packets. Each packet is dedicated to the data of a single edge, but may contain any number of data items. This setting limits the size of the packet in bytes. Packets should be large enough to drown out any fixed overheads, but small enough to allow good interleaving with other packets. Note that a single item cannot straddle packets, therefore the maximum packet size can exceed the value configured here by the size of a single data item. This setting has no effect on a non-distributed edge.

description: Sets the scaling factor used by the adaptive receive window sizing function. For each distributed edge the receiving member regularly sends flow-control ("ack") packets to its sender which prevent it from sending too much data and overflowing the buffers. The sender is allowed to send the data one `receive window` further than the last acknowledged byte and the receive window is sized in proportion to the rate of processing at the receiver. Ack packets are sent in regular intervals (InstanceConfig#setFlowControlPeriodMs) and the `receive window multiplier` sets the factor of the linear relationship between the amount of data processed within one such interval and the size of the receive window. To put it another way, let us define an `ackworth` as the amount of data processed between two consecutive ack packets. The receive window multiplier determines the number of ackworths the sender can be ahead of the last acked byte. This setting has no effect on a non-distributed edge.

description: If set to true, creating Hazelcast client does not wait for connecting to the cluster.

description: Defines the reconnection mode. The valid values are:\n * "ON": Enables reconnection in a blocking manner where all the waiting invocations are blocked until a cluster connection is established or failed. This is the default value.\n * "OFF": Disables the reconnection.\n * "ASYNC": Enables reconnection in a non-blocking manner where all the waiting invocations receive a HazelcastClientOfflineException.

description: Defines the configuration used when retrying to connect to the cluster.

description: Specifies how long to wait (backoff) after the first failure before retrying in milliseconds.

description: Specifies the upper limit for the backoff in milliseconds.

description: Factor to multiply the backoff after a failed retry.

description: Timeout value in milliseconds for the client to give up to connect to the current cluster Depending on FailoverConfig, a client can shutdown or start trying on alternative cluster after reaching the timeout. Its default value is -1. For the default value, the client will not stop trying to connect to the cluster. If the failover client is used, the client will start trying to connect alternative clusters after 120000 ms. For any other value, both the failover and non-failover client will use that as it is.

description: Specifies by how much to randomize backoffs.

description: If set to true, user code deployment is enabled.

description: Sequence lists the jar files containing the classes to load.

description: Sequence lists the classes available in the client class path to load.

description: The load balancer can be configured with the "load-balancer" mapping. It has a scalar sub-node called "type". The valid values for the type of the load balancer are:\n * "random": The member the operations to be sent to is chosen randomly.\n * "round-robin": The member the operations to be sent to is chosen in a round-robin fashion.\n * "custom": The member the operations to be sent to is chosen by provided load balancer implementation. The implementation class name is specified in additional "class-name" key.

description: Sets how many IDs are pre-fetched on the background when one call to FlakeIdGenerator#newId() is made.

description: Sets for how long the pre-fetched IDs can be used. If this time elapses, a new batch of IDs will be fetched. Time unit is milliseconds, default is 600,000 (10 minutes).

description: A policy to deal with an overloaded topic; so topic where there is no place to store new messages. This policy can only be used in combination with the com.hazelcast.core.HazelcastInstance#getReliableTopic(String). The reliable topic uses a com.hazelcast.ringbuffer.Ringbuffer to store the messages. A ringbuffer doesn't track where readers are, so it has no concept of a slow consumers. This provides many advantages like high performance reads, but it also gives the ability to the reader to re-read the same message multiple times in case of an error. A ringbuffer has a limited, fixed capacity. A fast producer may overwrite old messages that are still being read by a slow consumer. To prevent this, we may configure a time-to-live on the ringbuffer (see com.hazelcast.config.RingbufferConfig#setTimeToLiveSeconds(int). Once the time-to-live is configured, the TopicOverloadPolicy controls how the publisher is going to deal with the situation that a ringbuffer is full and the oldest item in the ringbuffer is not old enough to get overwritten. Keep in mind that this retention period (time-to-live) can keep messages from being overwritten, even though all readers might have already completed reading. Its default value is BLOCK. Available values are as follows: - DISCARD_OLDEST: Using this policy, a message that has not expired can be overwritten. No matter the retention period set, the overwrite will just overwrite the item. This can be a problem for slow consumers because they were promised a certain time window to process messages. But it will benefit producers and fast consumers since they are able to continue. This policy sacrifices the slow producer in favor of fast producers/consumers.\n * DISCARD_NEWEST: Message that was to be published is discarded.\n * BLOCK: The caller will wait until there is space in the Ringbuffer.\n * ERROR: The publish call fails immediately.

enum: realms username-password kerberos token credentials-factory

description: Defines a static UsernamePasswordCredentials instance as the member's identity. It has mandatory "username" and "password" attributes.

description: Defines a static TokenCredentials instance as the client's identity. It has a "value" and it can have also "encoding" defined.

description: Specifies the name and properties of your class that you developed by implementing Hazelcast's Credentials interface. This element has a mandatory "class-name" attribute where you should define the factory class implementing ICredentialsFactory used to create Credentials objects. With the "properties" child property, you can define properties for the factory class.

description: This sequence lets you list the members in your cluster the client is connecting to.

description: If true, client will route the key based operations to owner of the key at the best effort. Note that it uses a cached version of com.hazelcast.core.PartitionService#getPartitions() and doesn't guarantee that the operation will always be executed on the owner. The cached table is updated every second.

description: If true, client will redo the operations that were executing on the server and client lost the connection. This can be because of network, or simply because the member died. However it is not clear whether the application is performed or not. For idempotent operations this is harmless, but for non idempotent ones retrying can cause to undesirable effects. Note that the redo can perform on any member. If false, the operation will throw a RuntimeException that is wrapping a java.io.IOException.

description: Connection timeout is the timeout value in milliseconds for members to accept client connection requests. The following are the example configurations. Its default value is 5000.

description: Flag to enable icmp ping failure detector. When set to true, this client will use icmp ping failure detector to detect unavailable members.

description: Interval, in milliseconds, between each ping attempt. 1000ms (1 sec) is also the minimum interval allowed.

description: Number of milliseconds until a ping attempt is considered failed if there was no reply.

description: Maximum number of ping attempts before the member gets suspected by the detector.

description: Maximum number of hops the packets should go through. You can set to 0 to use your system���s default TTL.

description: The client will fail to start if it is unable to action an ICMP ping command when ICMP is enabled. Failure is usually due to OS level restrictions.

description: Set its "enabled" sub-element to true for cluster discovery in the Hazelcast Cloud infrastructure. You need to define the mandatory "discovery-token" sub-node used by the discovery mechanism.

description: Lets you add custom hooks to join and perform connection procedures (like a custom authentication protocol, etc.). This feature is available only in Hazelcast Enterprise. To be able to use it, you should first implement the MemberSocketInterceptor (for members joining to a cluster) or SocketInterceptor (for clients connecting to a member) class. Its configuration contains the class you implemented and socket interceptor properties. By default, it is disabled.

description: When enabled, it will walk through all available discovery strategies and detect the correct one for the current runtime environment. For example, it will automatically use the hazelcast-aws plugin if run on an AWS instance.

description: Lets you configure SSL using the SSL context factory. This feature is available only in Hazelcast Enterprise. To be able to use it, encryption should NOT be enabled and you should first implement your SSLContextFactory class. Its configuration contains the factory class and SSL properties. By default, it is disabled.

description: Enables/disables the TCP_NODELAY socket option.

description: Enables/disables the SO_KEEPALIVE socket option.

description: Enables/disables the SO_REUSEADDR socket option.

description: Enables/disables SO_LINGER with the specified linger time in seconds.

description: Sets the SO_SNDBUF and SO_RCVBUF options to the specified value in KB for this Socket.

description: Enables/disables Integrity Checker. Integrity Checker can be disabled to improve startup time.

description: Name of the data connection configuration.

description: The type of the DataConnection.

description: true if an instance of the data connection will be shared. Depending on the implementation of the data connection, the shared instance may be single a thread-safe instance, or not thread-safe, but a pooled instance; false when on each usage a new instance of the underlying resource should be created.The default is true.

description: The "properties" used for configuring data connection

description: Enabled Hazelcast TPC. Disabled by default.

description: Configures the number of eventloops. It's equal to available processor count by default.

description: Hazelcast TPC is the next generation of Hazelcast built with thread per core architecture. It's still being developed and everything is subject to change. TPC is disabled by default.

description: Configures the port range available for TPC sockets.

description: Configures SO_RCVBUF socket option for TPC sockets.

description: Configures SO_SNDBUF socket option for TPC sockets.

description: Socket configuration for TPC. In TPC, each eventloop has its own sockets.