All Downloads are FREE. Search and download functionalities are using the official Maven repository.

.hazelcast-all.3.5.1.source-code.hazelcast-spring-3.4.xsd Maven / Gradle / Ivy

There is a newer version: 5.0-BETA-1
Show newest version





    
        
            
                
                    
                        
                        
                        
                        
                        
                        
                        
                        
                        
                            
                                
                                
                                
                                    
                                        
                                            The number of executor threads per Member for the Executor.
                                        
                                    
                                
                                
                                    
                                        
                                            Executor's task queue capacity. 0 means Integer.MAX_VALUE.
                                        
                                    
                                
                            
                        
                        
                            
                                
                                    
                                        
                                            
                                                
                                            
                                        
                                    
                                    
                                        
                                            
                                                
                                            
                                            
                                            
                                            
                                            
                                            
                                        
                                    
                                
                                
                                
                                    
                                        
                                            Value of maximum size of items in the Queue.
                                        
                                    
                                
                                
                                    
                                        
                                            Count of synchronous backups. Remember that, Queue is a non-partitioned
                                            data structure, i.e. all entries of a Set resides in one partition. When
                                            this parameter is '1', it means there will be a backup of that Set in
                                            another node in the cluster. When it is '2', 2 nodes will have the backup.
                                        
                                    
                                
                                
                                    
                                        
                                            Count of asynchronous backups.
                                        
                                    
                                
                            
                        
                        
                            
                                
                                    
                                        
                                            
                                                
                                            
                                            
                                            
                                                
                                                    
                                                        Name of the class implementing MapLoader and/or MapStore.
                                                    
                                                
                                            
                                            
                                            
                                            
                                            
                                                
                                                    
                                                        Number of seconds to delay to call the MapStore.store(key,
                                                        value).
                                                        If the value is zero then it is write-through so
                                                        MapStore.store(key, value) will be called as soon as the
                                                        entry is updated. Otherwise it is write-behind so updates will
                                                        be stored after write-delay-seconds value by calling
                                                        Hazelcast.storeAll(map). Default value is 0.
                                                    
                                                
                                            
                                            
                                                
                                                    
                                                        Used to create batch chunks when writing map store. In default
                                                        mode all entries will be tried to persist in one go. To create
                                                        batch chunks, minimum meaningful value for write-batch-size is
                                                        2.
                                                        For values smaller than 2, it works as in default mode.
                                                    
                                                
                                            
                                            
                                                
                                                    
                                                        Setting write-coalescing is meaningful if you are using
                                                        write-behind map-store. Otherwise it has no effect.
                                                        When write-coalescing is true, only the latest
                                                        store operation on a key in the write-delay-seconds
                                                        time-window will be reflected to the map-store.
                                                    
                                                
                                            
                                            
                                                
                                                    
                                                        
                                                        
                                                    
                                                
                                            
                                        
                                    
                                    
                                    
                                        
                                            
                                                Hazelcast can replicate some or all of the cluster data. For example,
                                                you can have 5 different maps but you want only one of these maps
                                                replicating across clusters. To achieve this you mark the maps
                                                to be replicated by adding this element.
                                            
                                        
                                        
                                            
                                            
                                        
                                    
                                    
                                        
                                            
                                                This configuration lets you index the attributes and also order them.
                                            
                                        
                                        
                                            
                                                
                                                    
                                                        
                                                        
                                                    
                                                
                                            
                                        
                                    
                                    
                                        
                                            
                                                This configuration lets you add listeners (listener classes) for the
                                                map entries.
                                            
                                        
                                        
                                            
                                                
                                            
                                        
                                    
                                
                                
                                
                                    
                                        
                                            It is used to determine how the data will be stored in memory. It has two
                                            values: BINARY and OBJECT. BINARY is the default option and enables to
                                            store the data in serialized binary format. If OBJECT is set as the value,
                                            data will be stored in deserialized form.
                                        
                                    
                                

                                
                                    
                                        
                                            You can retrieve some statistics like owned entry count, backup entry count,
                                            last update time, locked entry count by setting this parameter's value
                                            as "true". The method for retrieving the statistics is `getLocalMapStats()`.
                                        
                                    
                                
                                
                                    
                                        
                                            This parameter is used to increase the speed of query processes in the map.
                                            It only works when `in-memory-format` is set as `BINARY` and performs
                                            a pre-caching on the entries queried.
                                        
                                    
                                
                                
                                    
                                        
                                            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 size. Any integer between 0 and Integer.MAX_VALUE. 0 means
                                            Integer.MAX_VALUE. Default is 0.
                                        
                                    
                                
                                
                                    
                                        
                                            When maximum size is reached, map is evicted based on the eviction policy
                                            defined. It has four attributes: PER_NODE (Maximum number of map entries in
                                            each JVM), PER_PARTITION (Maximum number of map entries within each
                                            partition),
                                            USED_HEAP_SIZE (Maximum used heap size in megabytes for each JVM) and
                                            USED_HEAP_PERCENTAGE (Maximum used heap size percentage for each JVM).
                                        
                                    
                                
                                
                                    
                                        
                                            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.
                                        
                                    
                                
                                
                                    
                                        
                                            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.
                                        
                                    
                                
                                
                                    
                                        
                                            Minimum time in milliseconds which should pass before checking if a
                                            partition of this map is evictable or not. Default value is 100 millis.
                                        
                                    
                                
                                
                                    
                                        
                                            Valid values are: NONE (no eviction), LRU (Least Recently Used), LFU
                                            (Least Frequently Used). NONE is the default.
                                        
                                    
                                
                                
                                    
                                        
                                            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'

This boolean parameter enables reading local backup entries when set as `true`.
When maximum size is reached, cache is evicted based on the eviction policy size: Size can be any integer between 0 and Integer.MAX_VALUE. Default value is 0. max-size-policy: Max-Size policy has these valid values: ENTRY_COUNT (Maximum number of cache entries in the cache), USED_NATIVE_MEMORY_SIZE (Maximum used native memory size in megabytes for each JVM), USED_NATIVE_MEMORY_PERCENTAGE (Maximum used native memory size percentage for each JVM), FREE_NATIVE_MEMORY_SIZE (Maximum free native memory size in megabytes for each JVM), FREE_NATIVE_MEMORY_PERCENTAGE (Maximum free native memory size percentage for each JVM). Default value is "ENTRY_COUNT". eviction-policy: Eviction policy has these valid values: LRU (Least Recently Used), LFU (Least Frequently Used). Default value is "LRU". List of cache entry listeners Name of the cache. the type of keys provided as full class name the type of values provided as full class name Defines whether statistics gathering is enabled on a cache. Defines whether management is enabled on a cache. Set if read-through caching should be used. Set if write-through caching should be used. Data 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 : keys and values will be stored in native memory. Defines the cache loader factory class name. Defines the cache writer factory class name. Defines the expiry policy factory class name. 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. 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. Type of value collection. It can be Set or List. Maximum size. Any integer between 0 and Integer.MAX_VALUE. 0 means Integer.MAX_VALUE. Default is 0. Count of synchronous backups. Remember that, List is a non-partitioned data structure, i.e. all entries of a List resides in one partition. When this parameter is '1', it means there will be a backup of that List in another node in the cluster. When it is '2', 2 nodes will have the backup. Count of asynchronous backups. Maximum size. Any integer between 0 and Integer.MAX_VALUE. 0 means Integer.MAX_VALUE. Default is 0. Count of synchronous backups. Remember that, Set is a non-partitioned data structure, i.e. all entries of a List resides in one partition. When this parameter is '1', it means there will be a backup of that List in another node in the cluster. When it is '2', 2 nodes will have the backup. Count of asynchronous backups. If set as `true`, you can retrieve statistics for the topic using the method `getLocalTopicStats()`. By default, it is false, meaning there is no global order guarantee by default. 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 an available savepoint. The chunk-size defined the number of emitted values before a chunk is sent 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). A replicated map is a fully vector clock based, eventually consistent implementation of the map interface. In difference to all other Hazelcast data structures this implementation is not partitioned but fully replicates all data to all members. Due to the nature of eventually consistency there is a chance of reading staled data and no guarantee is given to retrieve the same value on multiple get calls. ReplicatedMap was added in Hazelcast 3.2. Number of parallel mutexes to minimize contention on keys. The default value is 32 which is a good number for lots of applications. If higher contention is seen on writes to values inside of the replicated map this value can be adjusted to the needs. Defines a number of milliseconds after a put is executed before the value is replicated to other nodes. In this time multiple puts can be operated and are cached up to be send at once. This highers the latency for eventually consistency but lowers IO operations. Default value is 100ms before a replication is operated, if set to 0 no delay is used and all values are replicated one by one. This value defines it the replicated map is available for reads before the initial replication is completed. Default is true. If set to false no Exception will be thrown when replicated map is not yet ready but call will block until finished. Specify the name, type and value of your attribute here.
DataSerializableFactory class to be registered. PortableFactory class to be registered. Global serializer class to be registered if no other serializer is applicable. Defines the class name of the serializer implementation. element.]]> Encryption algorithm such as DES/ECB/PKCS5Padding, PBEWithMD5AndDES, AES/CBC/PKCS5Padding, Blowfish, DESede. Name of the principal. Wildcards(*) can be used. Name of the permission. Wildcards(*) can be used. Endpoint address of principal. Wildcards(*) can be used. Permission actions that are permitted on Hazelcast instance objects. Credentials className




© 2015 - 2024 Weber Informatics LLC | Privacy Policy