Chapter 1. Data Grid release information Learn about new features and get the latest Data Grid release information. 1.1. What is new in Data Grid 8.5.2 Data Grid 8.5.2 improves usability, increases performance, and enhances security. Find out what is new. Simple cache metrics updates Simple cache mode now provides the same metrics as the other cache modes such as local, distributed, replicated, and invalidation. This simplifies observing cache metrics in observing and alerting systems. Support for JDBC_PING2 protocol Data Grid 8.5.2 provides the ability to use JDBC_PING2 protocol for JGroups discovery. It is recommended to use the JDBC_PING2 protocol rather than JDBC_PING protocol with Data Grid 8.5.2. For more information, see JDBC_PING2 . Data Grid 8.5.2 security update Data Grid 8.5.2 provides a security enhancement to address CVEs. You must upgrade any Data Grid 8.5.1 deployments to version 8.5.2 as soon as possible. For more information see the advisory related to this release RHSA-2024:10214 . Important Vector search queries are not supported in Data Grid. 1.2. What's new in Data Grid 8.5.1 Data Grid 8.5.1 improves usability, increases performance, and enhances security. Find out what's new. Ability to automatically reload SSL/TLS certificates From Data Grid 8.5.1 onward, when certificates are renewed, Data Grid monitors keystore files for changes and automatically reloads these files, without requiring a server or client restart. Note To ensure seamless operations during certificate rotation, use certificates that are signed by a certificate authority (CA) and configure both server and client truststores with the CA certificate. For more information, see SSL/TLS Certificate rotation . Ability to index keys for indexed remote queries Data Grid 8.5.1 introduces an Indexed type for keys. You can index the keys in a cache for indexed remote queries by defining these keys as Indexed . This enhancement means that you can index the key fields as well as the value fields, which allows the keys to be used in Ickle queries. For more information, see Queries by keys . 1.3. What's new in Data Grid 8.5.0 Data Grid 8.5.0 improves usability, increases performance, and enhances security. Find out what's new. Data Grid 8.5.0 security update Data Grid 8.5.0 provides a security enhancement to address CVEs. You must upgrade any Data Grid 8.4 deployments to version 8.5.0 as soon as possible. For more information see the advisory related to this release RHSA-2024:4460 . Support for RESP protocol endpoint The Redis serialization protocol (RESP) protocol endpoint in RHDG, which was provided as a technology preview feature in releases, is now fully supported. Additionally, the 8.5 release provides more Redis commands that you can use. For more information, see Using the RESP protocol endpoint with Data Grid . getAndSet REST operation for strong counters This release introduces a new getAndSet REST (Representational State Transfer) operation for strong counters. The getAndSet operation atomically sets values for strong counters with POST requests. If the operation is successful, Data Grid returns the value in the payload. For more information, see Performing getAndSet atomic operations on strong counters . Aggregate security realm This release introduces a new security realm called aggregate security realm. You can use an aggregate security realm to combine multiple security realms: one for authentication and the others for authorization. For more information, see Aggregate security realm . New Memcached connector The RHDG 8.5 release replaces the old Memchached connector with a new connector. The new Memcached connector provides the following improvements: Support for both TEXT and BINARY protocols Ability to use security realms for authentication Support for TLS encryption Performance improvements Auto detection of protocol Note For RHDG to auto-detect text protocol, clients must send a "fake" SET operation to authenticate on connection. If this is not possible for the applications, you must create a Memcached connector on a dedicated port without authentication. Thread dump on CacheBackpressureFullException The most likely cause of CacheBackpressureFullException exception is either hung threads or server overload. Data Grid now creates periodic thread dumps on CacheBackpressureFullException so that you can analyze the cause. By default the interval between two thread dumps is 60 seconds. Ability to set a stable topology By default, after a cluster shutdown, Data Grid waits for all nodes to join the cluster and restore the topology. However, you can now mark the current topology stable for a specific cache by using a command by using either CLI or REST. CLI command For more information, see Setting a stable Topology . REST command For more information, see Set a Stable Topology . Enhancement to ProtoStream logging in MassIndexer MassIndexer now displays protobuf message name instead of a class name in log message for Protostream objects to improve clarity of the message. OpenTelemetry Tracing integration New spans have been introduced to add tracing capabilities to container, persistence, cluster, xsite, and security so that telemetry can be exported to and consumed by OpenTelemetry. Support for JBoss Marshalling JBoss Marshalling was deprecated in Data Grid 8.4.6 and earlier versions. It is fully supported in Data Grid 8.5.0. 1.4. Removal notice for Data Grid release 8.5.0 Data Grid release 8.5.0 removes the following features. RHDG clients The following HotRod clients are no longer provided with RHDG: .NET client C++ client node.js client However, you can continue using older clients with RHDG 8.5. Java EE dependencies Support for Java EE dependencies has been removed. All applications added to the RHDG server, and client HotRod applications must be updated to use Jakarta EE dependencies. JBoss EAP modules RHDG modules for Red Hat JBoss EAP applications are no longer distributed as a part of the RHDG release. JBoss EAP users can use the Infinispan subsystem that is integrated within the JBoss EAP product release without the need to separately install RHDG modules. For more information, see EAP 8 now supports full Infinispan functionality, including query, counters, locks, and CDI . JCache CDI support RHDG 8.5 removes support for JCache (JSR 107). As an alternative, use other caching API developments in the Jakarta EE ecosystem. Java 11 support RHDG 8.5 removes support for Java 11. The minimum supported Java version for RHDG 8.5 is Java 17. Client HotRod applications that require Java 11 can continue using older versions of client libraries. Tomcat session manager Tomcat session manager is not distributed with RHDG 8.5. RHDG server on Windows Deploying RHDG server on Windows Server 2019 is no longer supported. Spring support Using RHDG with Spring Boot 2.x and Spring 5.x is no longer supported. 1.5. Supported Java versions in Data Grid 8.5 Red Hat supports different Java versions, depending on how you install Data Grid. Removal of Java 11 support In Data Grid 8.5, support for Java 11 is removed. Users of Data Grid 8.5 must upgrade their applications at least to Java 17. You can continue using older Hot Rod Java client versions in combination with the latest Data Grid Server version. However, if you continue using older version of the client you will miss fixes and enhancements. Supported Java versions in Data Grid 8.5 Embedded caches Red Hat supports Java 17 and Java 21 when using Data Grid for embedded caches in custom applications. Remote caches Red Hat supports Java 17 and Java 21 for Data Grid Server installations. For Hot Rod Java clients, Red Hat supports Java 17 and Java 21. Red Hat supports Java 17 and Java 21 for Data Grid Server, Hot Rod Java clients, and when using Data Grid for embedded caches in custom applications. Note When running Data Grid Server on bare metal installations, the JavaScript engine is not available with Java 17. Additional resources Supported Configurations for Data Grid 8.5 Data Grid Deprecated Features and Functionality

Commands:
topology set-stable
POST /rest/v2/caches/{cacheName}?action=initialize&force={FORCE}