Hazelcast
Hazelcast allows you to use a portion of the memory on each node for caching without having to manage a separate
caching server or cluster. Hazelcast was the default implementation of the Cache interface until v1.26, when it
was decoupled from Para and moved to its own repository. We still
recommend the Hazelcast plugin for production use.
In Hazelcast, caches are organized by application id - each application has its own separate distributed map
with the same name.
These are the configuration properties for Hazelcast:
| Property | Default value | Description |
|---|---|---|
para.hc.async_enabled | false | Asynchronous operation when putting objects in cache. |
para.hc.eviction_policy | LRU | Cache eviction policy - LRU or LFU. |
para.hc.eviction_percentage | 25 | Cache eviction percentage. |
para.hc.ttl_seconds | 3600 | ‘Time To Live’ for cached objects in seconds. |
para.hc.max_size | 25 | Cache size as a percentage of used heap. |
para.hc.jmx_enabled | true | Enables JMX reporting. |
para.hc.ec2_discovery_enabled | true | Enables AWS EC2 auto discovery. |
para.hc.discovery_group | hazelcast | Security group for cloud discovery of nodes. |
para.hc.mancenter_enabled | !IN_PRODUCTION | Enables the Hazelcast Management Center. |
para.hc.mancenter_url | http://localhost:8001/mancenter | The URL for the Management Center server. |
In case you have enabled EC2 auto discovery, you must set para.hc.aws_access_key,
para.hc.aws_secret_key and para.hc.aws_region accordingly.