.hazelcast.5.3.6.source-code.hazelcast-client-config-4.0.xsd Maven / Gradle / Ivy
Controls if missing replacement value should lead to stop the boot process.
Specifies whether the the discovery strategy is enabled or not. Value can be true or false.
The maximum amount of time Hazelcast is going to try to connect to a well known member
before giving up. Please check if the specific discovery strategy supports this property.
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.
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.
One of membership-listener, instance-listener or migration-listener
Credentials className
Global serializer class to be registered if no other serializer is applicable.
Basic protection against untrusted deserialization based on class/package blacklisting and
whitelisting.
Java Serializable and Externalizable is prior to global serializer by default. If set true
the Java serialization step assumed to be handled by the global serializer.
Blacklisted classes and packages, which are not allowed to be deserialized.
Whitelisted classes and packages, which are allowed to be deserialized. If the list is empty
(no class or package name provided) then all classes are allowed.
Disables including default list entries (hardcoded in Hazelcast source code).
Name of a class to be included in the list.
Name of a package to be included in the list.
Class name prefix to be included in the list.
True to enable User Code Deployment on this client, false otherwise.
How many IDs are pre-fetched on the background when one call to newId() is made.
Value must be in the range 1..100,000, default is 100.
For how long the pre-fetched IDs can be used. If this time elapses, new IDs will be fetched.
Time unit is milliseconds.
If value is <= 0, validity is unlimited. Default value is 600,000 (10 minutes).
The IDs contain timestamp component, which ensures rough global ordering of IDs. If an ID
is assigned to an event that occurred much later, it will be much out of order.
If you don't need ordering, set this value to 0.
Name of the ID generator.
Policy to deal with an overloaded topic; so topic where there is no place to store new messages.
Options are
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.
DISCARD_NEWEST : The message that was to be published, is discarded.
BLOCK : The caller will wait till there space in the ringbuffer.
ERROR : The publish call immediately fails.(Default Value)
The maximum number of items to read in a batch.
Name of the Reliable Topic.
Sets the metrics collection frequency in seconds.
By default, metrics are collected every 5 seconds.
May be overridden by 'hazelcast.metrics.collection.frequency'
system property.
Master-switch for the metrics system. Controls whether
the metrics are collected and publishers are enabled.
May be overridden by 'hazelcast.metrics.enabled'
system property.
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.
May be overridden by 'hazelcast.metrics.jmx.enabled'
system property.
© 2015 - 2024 Weber Informatics LLC | Privacy Policy