Chapter 2. Data Grid Release Information

Data Grid includes Apache Log4j components in:

Data Grid 8.2.2 fixes CVE-2021-44228 which is a critical security vulnerability. Data Grid 8.2.3 fixes several Log4j CVEs of moderate severity. For more information, see the Data Grid 8.2 release notes or the Data Grid Operator 8.2 release notes. You can find the latest Data Grid documentation at Red Hat Data Grid Product Documentation.

If you cannot upgrade your Data Grid deployment, you must follow the steps to mitigate the critical vulnerability as outlined in the RHSB-2021-009 Log4Shell - Remote Code Execution security bulletin.

The Data Grid CLI includes a patch command that lets you manage and install server patches.

See Patching Data Grid Servers for instructions on downloading and installing server patches.

Data Grid servers expose the ability to perform rolling upgrades via the REST API.

See Performing Rolling Upgrades for steps on upgrading Data Grid clusters without downtime.

The Hot Rod client configuration API includes a RemoteCacheConfigurationBuilder class that lets you create and configure caches on first access either programmatically or via Hot Rod client properties file.

See the following documentation for more information:

The RemoteCacheManagerAdmin interface allows you to create caches with the org.infinispan cache configuration templates:

For example:

private void createCacheWithTemplate() {
    manager.administration().getOrCreateCache("myDistCache", "org.infinispan.DIST_SYNC");
    System.out.println("Cache created.");
}

private void createCacheWithTemplate() {
    manager.administration().getOrCreateCache("myDistCache", "org.infinispan.DIST_SYNC");
    System.out.println("Cache created.");
}

See org.infinispan.client.hotrod.RemoteCacheManagerAdmin for more information.

Configuration of Single File cache stores is simplified so you no longer need to set path or relative-to attributes. The location of Single File caches stores are always relative to the global persistent location.

See the following configuration documentation for more information:

Data Grid Operator lets you define the port where external services are exposed.

See Exposing Data Grid to External Clients for more information.

If you configure distributed caches with one owner (owners="1") then the conflict resolution strategy for partition handling must be ALLOW_READ_WRITES (when-split="ALLOW_READ_WRITES"), otherwise the cache configuration exception is thrown at server startup:

ISPN000575: PartitionStrategy must be ALLOW_READ_WRITES when numOwners is 1

ISPN000575: PartitionStrategy must be ALLOW_READ_WRITES when numOwners is 1

In the case of Data Grid service clusters on OpenShift, the Data Grid Operator automatically modifies configuration during upgrade to use when-split="ALLOW_READ_WRITES". This ensures that clusters restart when rolling upgrades take place.

For Data Grid servers running outside of OpenShift, you must modify cache configuration manually.

Data Grid 8.0 introduces a fully supported Data Grid Operator that provides operational intelligence to simplify Data Grid cluster deployment and management on Red Hat OpenShift.

Try some of the following documentation to create a Data Grid Operator subscription and get running in OpenShift:

Data Grid servers are no longer based on Red Hat JBoss Enterprise Application Platform (EAP), which reduces the memory and disk footprint and also simplifies configuration. In addition Data Grid 8.0 servers provide several enhancements and improvements to security, including integration with Red Hat SSO and a smaller attack surface.

See Getting Started with Data Grid Server and create a running Data Grid cluster in a few minutes.

Data Grid 8.0 includes a new console with improved management and administration capabilities.

To access the console, start Data Grid server and go to:
127.0.0.1:11222/console/

You can also access the console from Data Grid clusters running on OpenShift.

Data Grid 8.0 introduces REST API v2 with 50% faster response rates compared to v1 along more extensive capabilities.

Data Grid REST API v2 provides operations that let you:

Data Grid REST API v2 also automatically converts between storage formats such as JSON, XML, Protobuf, and plain text for increased inter-operability.

The Data Grid engineering team develop and maintain comprehensive REST API Documentation

In 8.0, Data Grid gives you a new CLI with intuitive commands for remotely accessing data and managing clusters.

The CLI uses familiar Bash commands for navigating, such as cd and ls. It also provides command history and auto-completion for ease of use. Additionally the CLI provide help text and man pages for commands with clear examples.

Try the docs: Getting Started with the Data Grid CLI.

Data Grid 8.0 is compatible with the Eclipse MicroProfile Metrics API and provides a /metrics endpoint for integration with Prometheus.

Data Grid metrics include:

Data Grid 8.0 also offers improved statistics and management operations via JMX and updates to logging with coarse-grained logging categories and support for logs in JSON format.

In 8.0, Data Grid marshalling capabilities are refactored so that user objects are isolated from internal objects, which improves efficiency and makes it easy to change between different Marshaller implementations.

Data Grid also now uses a ProtoStream API to store user types as Protocol Buffers, which is a platform-independent, language-neutral format that is highly customizable. As a result of this change, Data Grid 8.0 can also ensure binary compatibility of your data with future versions.

Find out about Data Grid Marshaller Implementations.

Data Grid 8.0 brings a number of performance improvements, notably: