This topic lists properties recognized and processed by Spring Data for VMware Tanzu GemFire and Spring Session for VMware Tanzu GemFire.
You can use these properties in Spring Boot application.properties
or as JVM System properties, to configure different aspects of or enable individual features of VMware GemFire in a Spring application. When combined with the power of Spring Boot, they give you the ability to quickly create an application that uses VMware GemFire.
Spring Data-Based Properties
The following properties all have a spring.data.gemfire.*
prefix. For example, to set the cache copy-on-read
property, use spring.data.gemfire.cache.copy-on-read
in Spring Boot application.properties
.
Miscellaneous Properties
Name | Description | Default | From |
---|---|---|---|
|
Name of the VMware GemFire server. |
|
|
|
Comma-delimited list of Locator endpoints formatted as:
|
[] |
|
|
Enable the Spring Data for VMware GemFire
|
|
|
GemFireCache Properties
Name | Description | Default | From |
---|---|---|---|
|
Configure whether a copy of an object returned from |
|
|
|
Percentage of heap at or above which the cache is considered in danger of becoming inoperable. |
|
|
|
Percentage of off-heap at or above which the cache is considered in danger of becoming inoperable. |
|
|
|
Whether to lookup Regions configured in VMware GemFire native configuration and declare them as Spring beans. |
|
|
|
Percentage of heap at or above which the eviction should begin on Regions configured for HeapLRU eviction. |
|
|
|
Percentage of off-heap at or above which the eviction should begin on Regions configured for HeapLRU eviction. |
|
|
|
Configure the log-level of a VMware GemFire cache. |
|
|
|
Alias for |
|
|
|
Name of a Spring bean that implements |
|
|
|
Comma-delimited list of Region names for which compression is configured. |
|
|
cache.off-heap.memory-size |
Determines the size of off-heap memory used by VMware GemFire in megabytes (m) or gigabytes (g) — for example, |
|
|
|
Comma-delimited list of Region names for which off-heap is configured. |
|
|
ClientCache Properties
Name | Description | Default | From |
---|---|---|---|
|
Used only for clients in a client/server installation. If set, this indicates that the client is durable and identifies the client. The ID is used by servers to reestablish any messaging that was interrupted by client downtime. |
|
|
|
Used only for clients in a client/server installation. Number of seconds this client can remain disconnected from its server and have the server continue to accumulate durable events for it. |
|
|
|
Whether the server should keep the durable client's queues alive for the timeout period. |
|
|
Peer Cache Properties
Name | Description | Default | From |
---|---|---|---|
|
Whether a member (a Locator or Server) try to reconnect and reinitialize the cache after it has been forced out of the cluster by a network partition event or has otherwise been shunned by other members. |
|
|
|
The length, in seconds, of distributed lock leases obtained by this cache. |
|
|
|
The number of seconds a cache operation waits to obtain a distributed lock lease. |
|
|
|
The frequency (in seconds) at which a message is sent by the primary cache-server to all the secondary cache-server nodes to remove the events that have already been dispatched from the queue. |
|
|
|
The number of seconds a cache get operation can spend searching for a value. |
|
|
|
Whether this cache member node pulls its configuration metadata from the cluster-based cluster configuration service. |
|
|
CacheServer Properties
Name | Description | Default | From |
---|---|---|---|
|
Whether the |
|
|
|
The IP address or hostname on which this cache server listens. |
|
|
|
The IP address or hostname that server locators tell to clients to indicate the IP address on which the cache server listens. |
|
|
|
The frequency in milliseconds at which to poll the load probe on this cache server. |
|
|
|
The maximum client connections. |
|
|
|
The maximum number of messages that can be in a client queue. |
|
|
|
The maximum number of threads allowed in this cache server to service client requests. |
|
|
|
The maximum amount of time between client pings. |
|
|
|
The time (in seconds) after which a message in the client queue expires. |
|
|
|
The port on which this cache server listens for clients. |
|
|
|
The buffer size of the socket connection to this |
|
|
|
The capacity of the client queue. |
|
|
|
The name of the disk store for client subscription queue overflow. |
|
|
|
The eviction policy that is executed when the capacity of the client subscription queue is reached. |
|
|
|
The outgoing socket connection tcp-no-delay setting. |
|
|
CacheServer
properties can be further targeted at specific CacheServer
instances by using an optional bean name of the CacheServer
bean defined in the Spring ApplicationContext
. Consider the following example:
spring.data.gemfire.cache.server.[<cacheServerBeanName>].bind-address=...
Cluster Properties
Name | Description | Default | From |
---|---|---|---|
|
Specifies the data management policy used when creating Regions on the servers in the cluster. |
|
|
DiskStore Properties
Name | Description | Default | From |
---|---|---|---|
|
Whether to allow |
|
|
|
Whether to cause the disk files to be automatically compacted. |
|
|
|
The threshold at which an oplog becomes compactible. |
|
|
|
The system directory where the |
|
|
|
The amount of disk space allowed to store disk store (oplog) files. |
|
|
|
The critical threshold for disk usage as a percentage of the total disk volume. |
|
|
|
The warning threshold for disk usage as a percentage of the total disk volume. |
|
|
|
The maximum size (in megabytes) a single oplog (operation log) can be. |
|
|
|
The maximum number of operations that can be asynchronously queued. |
|
|
|
The number of milliseconds that can elapse before data written asynchronously is flushed to disk. |
|
|
|
The number of segments the DiskStore will be organized into. |
|
|
|
Configures the write buffer size in bytes. |
|
|
DiskStore
properties can be further targeted at specific DiskStore
instances by setting the DiskStore.name
property (see VMware GemFire Java API Reference).
For example, you can specify directory location of the files for a specific, named DiskStore
by using:
spring.data.gemfire.disk.store.Example.directory.location=/path/to/gemfire/disk-stores/Example/
The directory location and size of the DiskStore
files can be further divided into multiple locations and size using array syntax:
spring.data.gemfire.disk.store.Example.directory[0].location=/path/to/gemfire/disk-stores/Example/one
spring.data.gemfire.disk.store.Example.directory[0].size=4096000
spring.data.gemfire.disk.store.Example.directory[1].location=/path/to/gemfire/disk-stores/Example/two
spring.data.gemfire.disk.store.Example.directory[1].size=8192000
Both the name and array index are optional, and you can use any combination of name and array index. Without a name, the properties apply to all DiskStore
instances. Without array indexes, all named DiskStore
files are stored in the specified location and limited to the defined size.
Entity Properties
Name | Description | Default | From |
---|---|---|---|
|
Comma-delimited list of package names indicating the start points for the entity scan. |
|
Locator Properties
Name | Description | Default | From |
---|---|---|---|
|
The IP address or hostname of the system NIC to which the embedded Locator is bound to listen for connections. |
|
|
locator.port |
The network port to which the embedded Locator will listen for connections. |
|
|
Logging Properties
Name | Description | Default | From |
---|---|---|---|
|
The log level of an VMware GemFire cache. Alias for 'spring.data.gemfire.cache.log-level'. |
|
|
|
The amount of disk space allowed to store log files. |
|
|
|
The pathname of the log file used to log messages. |
|
|
|
The maximum size of a log file before the log file is rolled. |
|
Management Properties
Name | Description | Default | From |
---|---|---|---|
|
Whether to use the HTTP protocol to communicate with a VMware GemFire Manager. |
|
|
|
The IP address or hostname of the VMware GemFire Manager that runs the HTTP service. |
|
|
|
The port used by the VMware GemFire Manager's HTTP service to listen for connections. |
|
|
Manager Properties
Name | Description | Default | From |
---|---|---|---|
|
The access control list (ACL) file used by the Manager to restrict access to the JMX MBeans by the clients. |
|
|
manager.bind-address |
The IP address or hostname of the system NIC used by the Manager to bind and listen for JMX client connections. |
|
|
|
The hostname given to JMX clients to ask the Locator for the location of the Manager. |
|
|
|
By default, the JMX Manager lets clients without credentials connect. If this property is set to the name of a file, only clients that connect with credentials that match an entry in this file are allowed. |
|
|
|
The port used by the Manager to listen for JMX client connections. |
|
|
|
Whether to start the Manager service at runtime. |
|
|
|
The rate, in milliseconds, at which this member pushes updates to any JMX Managers. |
|
|
PDX Properties
Name | Description | Default | From |
---|---|---|---|
|
The name of the |
|
|
|
Whether PDX ignores fields that were unread during deserialization. |
|
|
|
Whether PDX persists type metadata to disk. |
|
|
|
Whether a Region entry is returned as a |
|
|
|
The name of a custom Spring bean that implements |
|
Pool Properties
Name | Description | Default | From |
---|---|---|---|
|
The timeout used to acquire a free connection from a Pool. |
|
|
|
The amount of time a connection can be idle before expiring (and closing) the connection. |
|
|
|
The interval for how frequently the Pool checks to see if a connection to a given server should be moved to a different server to improve the load balance. |
|
|
|
Comma-delimited list of locator endpoints in the format of |
|
|
|
The maximum number of client to server connections that a Pool will create. |
|
|
|
The minimum number of client to server connections that a Pool maintains. |
|
|
|
Whether the created Pool can be used by multiple authenticated users. |
|
|
|
How often to ping servers to verify that they are still alive. |
|
|
|
Whether to perform single-hop data access operations between the client and servers. When |
|
|
|
The number of milliseconds to wait for a response from a server before timing out the operation and trying another server (if any are available). |
|
|
|
Whether to signal the server that the client is prepared and ready to receive events. |
|
|
|
The number of times to retry a request after timeout/exception. |
|
|
|
The group that all servers to which a Pool connects must belong. |
|
|
|
Comma-delimited list of |
|
|
|
The socket buffer size for each connection made in all Pools. |
|
|
|
How often to send client statistics to the server. |
|
|
pool.subscription-ack-interval |
The interval in milliseconds to wait before sending acknowledgements to the |
|
|
|
Whether the created Pool has server-to-client subscriptions enabled. |
|
|
|
The |
|
|
|
The redundancy level for all Pools server-to-client subscriptions. |
|
|
|
The thread local connections policy for all Pools. |
|
|
Security Properties
Name | Description | Default | From |
---|---|---|---|
|
The name of the user used to authenticate with the servers. |
|
|
|
The user password used to authenticate with the servers. |
|
|
|
The system pathname to a properties file that contains security credentials. |
|
|
|
X |
X |
|
|
The callback that should be invoked in the post-operation phase, which is when the operation has completed on the server but before the result is sent to the client. |
|
|
|
Static creation method that returns an |
|
|
|
Static creation method that returns an |
|
|
|
Used for authentication. For secure transmission of sensitive credentials (such as passwords), you can encrypt the credentials by using the Diffie-Hellman key-exchange algorithm. You can do so by setting the |
|
|
|
The pathname to a log file used for security log messages. |
|
|
|
The log level for security log messages. |
|
|
|
The name of a class that implements |
|
|
|
Static creation method that returns an |
|
|
|
Static creation method that returns an |
|
|
security.peer.verify-member-timeout |
The timeout in milliseconds used by a peer to verify membership of an unknown authenticated peer requesting a secure connection. |
|
|
|
The name of a class that implements the |
|
|
|
The VMware GemFire System property that refers to the location of an Apache Shiro INI file that configures the Apache Shiro Security Framework in order to secure VMware GemFire. |
|
SSL Properties
Name | Description | Default | From |
---|---|---|---|
|
The alias to the stored SSL certificate used by the cluster to secure communications. |
|
|
|
The default alias to the stored SSL certificate used to secure communications across the entire VMware GemFire system. |
|
|
|
The alias to the stored SSL certificate used by the WAN Gateway Senders/Receivers to secure communications. |
|
|
|
The alias to the stored SSL certificate used by the Manager's JMX-based JVM MBeanServer and JMX clients to secure communications. |
|
|
|
The alias to the stored SSL certificate used by the Locator to secure communications. |
|
|
|
The alias to the stored SSL certificate used by clients and servers to secure communications. |
|
|
|
The alias to the stored SSL certificate used by the embedded HTTP server to secure communications (HTTPS). |
|
|
|
Comma-separated list of SSL ciphers or |
|
|
|
Comma-delimited list of VMware GemFire components (for example, WAN) to be configured for SSL communication. |
|
|
|
The system pathname to the Java KeyStore file storing certificates for SSL. |
|
|
|
The password used to access the Java KeyStore file. |
|
|
|
The password used to access the Java KeyStore file (for example, JKS). |
|
|
|
Comma-separated list of SSL protocols or |
|
|
|
Whether two-way authentication is required. |
|
|
|
The system pathname to the trust store (Java KeyStore file) that stores certificates for SSL. |
|
|
|
The password used to access the trust store (Java KeyStore file). |
|
|
|
The password used to access the trust store (ex. Java KeyStore (JKS) file). |
|
|
|
Whether two-way HTTP authentication is required. |
|
|
Service Properties
Name | Description | Default | From |
---|---|---|---|
|
The IP address or hostname of the system NIC used by the embedded HTTP server to bind and listen for HTTP(S) connections. |
|
|
|
The port used by the embedded HTTP server to listen for HTTP(S) connections. |
|
|
|
Whether two-way HTTP authentication is required. |
|
|
|
Whether to start the Developer REST API web service. A full installation of VMware GemFire is required, and you must set the |
|
|
|
The port of the embedded Memcached server (service). |
|
|
|
The protocol used by the embedded Memcached server (service). |
|
|
Spring Session-Based Properties
The following properties all have a spring.session.data.gemfire.*
prefix. For example, to set the session Region name, set spring.session.data.gemfire.session.region.name
in Spring Boot application.properties
.
Spring Session Properties
Name | Description | Default | From |
---|---|---|---|
|
Name of the pool used to send data access operations between the client and servers. |
|
|
|
The |
|
|
|
The |
|
|
|
The names of session attributes for which an Index is created. |
|
|
|
Configures the number of seconds in which a session can remain inactive before it expires. |
|
|
|
The name of the (client/server) Region used to manage (HTTP) session state. |
|
|
|
The name of a Spring bean that implements |
|
While we do not recommend using VMware GemFire properties directly in your Spring applications, Spring Boot for Tanzu GemFire does not prevent you from doing so. See the complete reference to the VMware GemFire specific properties.
VMware GemFire is very strict about the properties that may be specified in a
gemfire.properties
file. You cannot mix Spring properties withgemfire.*
properties in a VMware GemFiregemfire.properties
file.
Content feedback and comments