| Name | Type | Default | Description |
|---|---|---|---|
| bucketPrefix | string | A string that is prepended to generated buckets or containers on the cloud store. Buckets or containers are named {bucketPrefix}-{cacheName}. | |
| cloudService | string | The cloud service to use. Supported values are dependent on the included version of the JClouds library. | |
| cloudServiceLocation | string | DEFAULT | The data center to use. Note that this is specific to the cloud provider in question. E.g., Amazon's S3 service supports storage buckets in several different locations. Optional, and defaults to DEFAULT |
| compress | boolean | true | Whether to compress stored data. Defaults to true |
| identity | string | A String that identifies you to the cloud provider. For example. with AWS, this is your ACCESS KEY. | |
| lazyPurgingOnly | boolean | false | If enabled, then expired entries are only purged on access, lazily, rather than by using the periodic eviction thread. Defaults to false |
| maxConnections | int | 10 | The maximum number of concurrent connections to make to the cloud provider. Defaults to 10. |
| requestTimeout | int | 10000 | A timeout to use when communicating with the cloud storage provider, in milliseconds. Defaults to 10000. |
| password | string | A String that is used to authenticate you with the cloud provider. For example. with AWS, this is your SECRET KEY. | |
| proxyHost | string | The host name of a proxy to use. Optional, no proxy is used if this is un-set. | |
| proxyPort | int | The port of a proxy to use. | |
| secure | boolean | true | Whether to use secure (SSL) connections or not. Defaults to true |
| Name | Type | Default | Description |
|---|---|---|---|
| fetchPersistentState | boolean | If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled. Persistent state transfer with a shared cache store does not make sense, as the same persistent store that provides the data will just end up receiving it. Therefore, if a shared cache store is used, the cache will not allow a persistent state transfer even if a cache store has this property set to true. Finally, setting it to true only makes sense if in a clustered environment, and only 'replication' and 'invalidation' cluster modes are supported. | |
| ignoreModifications | boolean | If true, any operation that modifies the cache (put, remove, clear, store...etc) won't be applied to the cache store. This means that the cache store could become out of sync with the cache. | |
| purgeOnStartup | boolean | If true, purges this cache store when it starts up. | |
| purgeSynchronously | boolean | If true, CacheStore#purgeExpired() call will be done synchronously | |
| purgerThreads | int | The number of threads to use when purging asynchronously. |
async?
Configuration for the async cache loader. If enabled, this provides you with asynchronous writes to the cache store, giving you 'write-behind' caching.
| Name | Type | Default | Description |
|---|---|---|---|
| enabled | boolean | If true, all modifications to this cache store happen asynchronously, on a separate thread. | |
| flushLockTimeout | long | Timeout to acquire the lock which guards the state to be flushed to the cache store periodically. | |
| modificationQueueSize | int | Sets the size of the modification queue for the async store. If updates are made at a rate that is faster than the underlying cache store can process this queue, then the async store behaves like a synchronous store for that period, blocking until the queue can accept more elements. | |
| shutdownTimeout | long | Timeout to stop the cache store. When the store is stopped it's possible that some modifications still need to be applied; you likely want to set a very large timeout to make sure to not loose data | |
| threadPoolSize | int | Size of the thread pool whose threads are responsible for applying the modifications. |
singletonStore?
SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store. The coordinator of the cluster will be responsible for the underlying CacheStore. SingletonStore is a simply facade to a real CacheStore implementation. It always delegates reads to the real CacheStore.
| Name | Type | Default | Description |
|---|---|---|---|
| pushStateTimeout | long | If pushStateWhenCoordinator is true, this property sets the maximum number of milliseconds that the process of pushing the in-memory state to the underlying cache loader should take. | |
| pushStateWhenCoordinator | boolean | If true, when a node becomes the coordinator, it will transfer in-memory state to the underlying cache store. This can be very useful in situations where the coordinator crashes and there's a gap in time until the new coordinator is elected. | |
| enabled | boolean | If true, the singleton store cache store is enabled. |
properties?
Properties passed to the cache store or loader
property*
| Name | Type | Default | Description |
|---|---|---|---|
| name | string | The property name or key | |
| value | string | The property value |