.hazelcast.3.6.8.source-code.hazelcast-config-3.2.xsd Maven / Gradle / Ivy
Number of sync backups. If 1 is set as the backup-count for example,
then all entries of the map will be copied to another JVM for
fail-safety. Valid numbers are 0 (no backup), 1, 2 ... 6.
Number of async backups. If 1 is set as the backup-count for example,
then all entries of the map will be copied to another JVM for
fail-safety. Valid numbers are 0 (no backup), 1, 2 ... 6.
Maximum number of seconds for each entry to stay in the map. Entries that are
older than <time-to-live-seconds> and not updated for <time-to-live-seconds>
will get automatically evicted from the map.
Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. Default is 0.
Maximum number of seconds for each entry to stay idle in the map. Entries that are
idle(not touched) for more than <max-idle-seconds> will get
automatically evicted from the map. Entry is touched if get, put or containsKey is called.
Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. Default is 0.
Valid values are:
NONE (no eviction),
LRU (Least Recently Used),
LFU (Least Frequently Used).
NONE is the default.
Maximum size.
Any integer between 0 and Integer.MAX_VALUE. 0 means Integer.MAX_VALUE. Default is 0.
When max. size is reached, specified percentage of the map will be evicted. Any integer between
0 and 100.
If 25 is set for example, 25% of the entries will get evicted.
While recovering from split-brain (network partitioning), map entries in the small cluster will
merge into the bigger cluster
based on the policy set here. When an entry merge into the cluster, there might an existing
entry with the same key already.
Values of these entries might be different for that same key. Which value should be set for the
key?
Conflict is resolved by the policy set here.
There are built-in merge policies such as:
com.hazelcast.map.merge.PassThroughMergePolicy; entry will be added if there is no
existing entry for the key.
com.hazelcast.map.merge.PutIfAbsentMapMergePolicy ; entry will be added if the merging
entry doesn't exist in the cluster.
com.hazelcast.map.merge.HigherHitsMapMergePolicy ; entry with the higher hits wins.
com.hazelcast.map.merge.LatestUpdateMapMergePolicy ; entry with the latest update wins.
Default policy is 'com.hazelcast.map.merge.PutIfAbsentMapMergePolicy'
Maximum size.
Any integer between 0 and Integer.MAX_VALUE. 0 means Integer.MAX_VALUE. Default is 0.
Maximum size.
Any integer between 0 and Integer.MAX_VALUE. 0 means Integer.MAX_VALUE. Default is 0.
Maximum size.
Any integer between 0 and Integer.MAX_VALUE. 0 means Integer.MAX_VALUE. Default is 0.
The JobTracker configuration is used to setup behavior of the Hazelcast MapReduce framework.
Every JobTracker is capable of running multiple map reduce jobs at once and so once configuration
is meant as a shared resource for all jobs created by the same JobTracker.
The configuration gives full control over the expected load behavior and thread counts to be used.
The max-thread-size setting configures the maximum thread pool size of the JobTracker.
The queue-size defines the maximum number of tasks are able to wait to be processed. A
value of 0 means unbounded queue.
retry-count is currently not used but reserved for later use where the framework will
automatically try to restart / retry operations from a available savepoint.
The chunk-size defined the number of emitted values before a chunk is send to the reducers.
If your emitted values are big or you want to better balance your work you might want to
change this to a lower or higher value.
A value of 0 means immediate transmission but remember that low values mean higher traffic
costs.
A very high value might cause an OutOfMemoryError to occur if emitted values not fit into
heap memory before being send to reducers. To prevent this you might want to use a combiner
to pre-reduce values on mapping nodes.
The communicate-stats setting defines if statistics (for example about processed entries)
are transmitted to the job emitter. This might be used to show any kind of progress to
an user inside of an UI system but produces additional traffic. If not needed you might
want to deactivate this.
The topology-changed-strategy defines how the map reduce framework will react on topology
changes while executing a job.
Currently only CANCEL_RUNNING_OPERATION is fully supported which throws an exception to
the job emitter (throws com.hazelcast.mapreduce.TopologyChangedException).
encryption algorithm such as
DES/ECB/PKCS5Padding,
PBEWithMD5AndDES,
AES/CBC/PKCS5Padding,
Blowfish,
DESede
Executor's task queue capacity. 0 means Integer.MAX_VALUE.
Endpoint address of principal. Wildcards(*) can be used.
Name of the principal. Wildcards(*) can be used.
Name of the permission. Wildcards(*) can be used.
Permission actions that are permitted on Hazelcast instance objects.
One of membership-listener, instance-listener or migration-listener