123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192 |
- <?xml version="1.0" encoding="UTF-8"?>
- <hazelcast xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-basic.xsd"
- xmlns="http://www.hazelcast.com/schema/config"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <group>
- <name>dev</name>
- <password>dev-pass</password>
- </group>
- <network>
- <port auto-increment="true">5701</port>
- <join>
- <multicast enabled="true">
- <multicast-group>224.2.2.3</multicast-group>
- <multicast-port>54327</multicast-port>
- </multicast>
- <tcp-ip enabled="false">
- <interface>127.0.0.1</interface>
- </tcp-ip>
- </join>
- <interfaces enabled="true">
- <interface>192.168.1.*</interface>
- </interfaces>
- <symmetric-encryption enabled="false">
- <!--
- encryption algorithm such as
- DES/ECB/PKCS5Padding,
- PBEWithMD5AndDES,
- AES/CBC/PKCS5Padding,
- Blowfish,
- DESede
- -->
- <algorithm>PBEWithMD5AndDES</algorithm>
- <!-- salt value to use when generating the secret key -->
- <salt>thesalt</salt>
- <!-- pass phrase to use when generating the secret key -->
- <password>thepass</password>
- <!-- iteration count to use when generating the secret key -->
- <iteration-count>19</iteration-count>
- </symmetric-encryption>
- <asymmetric-encryption enabled="false">
- <!-- encryption algorithm -->
- <algorithm>RSA/NONE/PKCS1PADDING</algorithm>
- <!-- private key password -->
- <keyPassword>thekeypass</keyPassword>
- <!-- private key alias -->
- <keyAlias>local</keyAlias>
- <!-- key store type -->
- <storeType>JKS</storeType>
- <!-- key store password -->
- <storePassword>thestorepass</storePassword>
- <!-- path to the key store -->
- <storePath>keystore</storePath>
- </asymmetric-encryption>
- </network>
- <executor-service>
- <core-pool-size>16</core-pool-size>
- <max-pool-size>64</max-pool-size>
- <keep-alive-seconds>60</keep-alive-seconds>
- </executor-service>
- <queue name="default">
- <!--
- Maximum size of the queue. When a JVM's local queue size reaches the maximum,
- all put/offer operations will get blocked until the queue size
- of the JVM goes down below the maximum.
- Any integer between 0 and Integer.MAX_VALUE. 0 means
- Integer.MAX_VALUE. Default is 0.
- -->
- <max-size-per-jvm>0</max-size-per-jvm>
- <!--
- Maximum number of seconds for each item to stay in the queue. Items that are
- not consumed in <time-to-live-seconds> will automatically
- get evicted from the queue.
- Any integer between 0 and Integer.MAX_VALUE. 0 means
- infinite. Default is 0.
- -->
- <time-to-live-seconds>0</time-to-live-seconds>
- </queue>
- <map name="default">
- <!--
- Number of 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, 3.
- -->
- <backup-count>1</backup-count>
- <!--
- Valid values are:
- NONE (no eviction),
- LRU (Least Recently Used),
- LFU (Least Frequently Used).
- NONE is the default.
- -->
- <eviction-policy>NONE</eviction-policy>
- <!--
- Maximum size of the map. When max size is reached,
- map is evicted based on the policy defined.
- Any integer between 0 and Integer.MAX_VALUE. 0 means
- Integer.MAX_VALUE. Default is 0.
- -->
- <max-size>0</max-size>
- <!--
- 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.
- -->
- <eviction-percentage>25</eviction-percentage>
- <!--
- 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. Default policy is hz.ADD_NEW_ENTRY
- There are built-in merge policies such as
- hz.NO_MERGE ; no entry will merge.
- hz.ADD_NEW_ENTRY ; entry will be added if the merging entry's key
- doesn't exist in the cluster.
- hz.HIGHER_HITS ; entry with the higher hits wins.
- hz.LATEST_UPDATE ; entry with the latest update wins.
- -->
- <merge-policy>hz.ADD_NEW_ENTRY</merge-policy>
- </map>
- <!-- Add your own map merge policy implementations here:
- <merge-policies>
- <map-merge-policy name="MY_MERGE_POLICY">
- <class-name>com.acme.MyOwnMergePolicy</class-name>
- </map-merge-policy>
- </merge-policies>
- -->
- <map name="AlfrescoFilesysCache">
- <!--
- Number of 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, 3.
- -->
- <backup-count>1</backup-count>
- <!--
- Valid values are:
- NONE (no eviction),
- LRU (Least Recently Used),
- LFU (Least Frequently Used).
- NONE is the default.
- -->
- <eviction-policy>NONE</eviction-policy>
- <!--
- Maximum size of the map. When max size is reached,
- map is evicted based on the policy defined.
- Any integer between 0 and Integer.MAX_VALUE. 0 means
- Integer.MAX_VALUE. Default is 0.
- -->
- <max-size>0</max-size>
- <!--
- 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.
- -->
- <eviction-percentage>25</eviction-percentage>
- <!--
- 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. Default policy is hz.ADD_NEW_ENTRY
- There are built-in merge policies such as
- hz.NO_MERGE ; no entry will merge.
- hz.ADD_NEW_ENTRY ; entry will be added if the merging entry's key
- doesn't exist in the cluster.
- hz.HIGHER_HITS ; entry with the higher hits wins.
- hz.LATEST_UPDATE ; entry with the latest update wins.
- -->
- <merge-policy>hz.ADD_NEW_ENTRY</merge-policy>
- <!--
- <near-cache>
- <time-to-live-seconds>5</time-to-live-seconds>
- <max-idle-seconds>60</max-idle-seconds>
- <eviction-policy>LRU</eviction-policy>
- <max-size>1000</max-size>
- <invalidate-on-change>true</invalidate-on-change>
- </near-cache>
- -->
- </map>
-
- </hazelcast>
|