Red Hat Summit7.0.0 Release Notes
Red Hat JBoss Data Grid 7.0
Known and resolved issues for Red Hat JBoss Data Grid 7.0.0
Abstract
The Red Hat JBoss Data Grid 7.0.0 Release Notes list and provide descriptions for a series of bugzilla bugs. The bugs highlight issues that are known problems and resolved issues for the release.
Chapter 1. Introduction to Red Hat JBoss Data Grid 7.0
Copy linkLink copied to clipboard!
Welcome to Red Hat JBoss Data Grid 7.0.0. As you become familiar with the newest version of JBoss Data Grid these Release Notes provide you with information about new features, as well as known and resolved issues. Use this document in conjunction with the entire JBoss Data Grid documentation suite, available at the Red Hat Customer Service Portal's JBoss Data Grid documentation page.
1.1. About Red Hat JBoss Data Grid
Copy linkLink copied to clipboard!
Red Hat's JBoss Data Grid is an open source, distributed, in-memory key/value data store built from the Infinispan open source software project. Whether deployed in client/server mode or embedded in a Java Virtual Machine, it is built to be elastic, high performance, highly available and to scale linearly.
JBoss Data Grid is accessible for both Java and Non-Java clients. Using JBoss Data Grid, data is distributed and replicated across a manageable cluster of nodes, optionally written to disk and easily accessible using the REST, Memcached and Hot Rod protocols, or directly in process through a traditional Java Map API.
1.2. Overview
Copy linkLink copied to clipboard!
This document contains information about the known issues of Red Hat JBoss Data Grid version 7.0.0. Customers are requested to read this documentation prior to installing this version.
Chapter 2. New Features and Enhancements
Copy linkLink copied to clipboard!
2.1. Distributed Streams
Copy linkLink copied to clipboard!
Red Hat JBoss Data Grid (JDG) 7.0 introduces a distributed version of the Java 8 Stream API which enables you to perform rich analytics operations on data stored in JDG using the functional expressions available in the Stream API.
Distributed Stream is a Library mode feature, but can also be executed on JDG Server using the new Remote Task Execution feature.
2.2. Remote Task Execution
Copy linkLink copied to clipboard!
JDG 7.0 features the ability to execute tasks (business logic) on JDG Server from the Java Hot Rod client. The task can be expressed as a Java executable loaded on JDG Server or as stored JavaScript procedure which executes on the Java 8 (Nashorn) scripting engine on JDG Server.
Remote Task Execution applies to Client-Server mode.
2.3. Apache Spark Integration
Copy linkLink copied to clipboard!
JDG 7.0 introduces a Resilient Distributed Dataset (RDD) and Discretized Stream (DStream) integration with Apache Spark version 1.6. This enables you to use JDG as a highly scalable, high-performance data source for Apache Spark, executing Spark and Spark Streaming operations on data stored in JDG.
The Apache Spark integration is available in Client-Server mode.
2.4. Apache Hadoop Integration
Copy linkLink copied to clipboard!
JDG 7.0 features a Hadoop InputFormat/OutputFormat integration, which enables use of JDG as a highly scalable, high performance data source for Hadoop. This enables use of tools from the Hadoop ecosystem which support InputFormat/OutputFormat for processing on data stored in JDG.
The Hadoop integration is available in Client-Server mode.
2.5. New Administration Console for Server deployments
Copy linkLink copied to clipboard!
JDG 7.0 introduces a new Administration Console which enables you to view a JDG cluster and perform clustered operations across its nodes. Operations include creation of new caches and cache templates, starting or stopping the cluster, adding or removing nodes, and deploying or executing remote tasks.
The Administration Console is a Client-Server mode feature and requires JDG Server deployed in Domain Mode.
2.6. Controlled shutdown and restart of cluster
Copy linkLink copied to clipboard!
JDG 7.0 adds the ability to shutdown or restart a cluster in a controlled manner, with data restore from persistent storage.
This feature is available in Client-Server mode.
2.7. Node.js (JavaScript) Hot Rod client
Copy linkLink copied to clipboard!
JDG 7.0 introduces a new Node.js (JavaScript) Hot Rod client, which enables you to use JDG as a high performance distributed in-memory NoSQL store from Node.js applications.
This feature is applicable to Client-Server mode.
2.8. Cassandra Cache Store
Copy linkLink copied to clipboard!
JDG 7.0 introduces a new out-of-the-box Cassandra cache store, which enables you to persist the entries of a distributed cache on a shared Apache Cassandra instance.
The Cassandra cache store is available in both Library and Client-Server modes.
2.9. Hot Rod C++ Enhancements
Copy linkLink copied to clipboard!
JDG 7.0 introduces asynchronous operations, querying, remote task invocation, and encryption of client/server communication using TLS/SSL, as Technical Preview features in the Hot Rod C++ client .
These enhancements are applicable to Client-Server mode.
2.10. Hot Rod C# Enhancements
Copy linkLink copied to clipboard!
JDG 7.0 introduces querying, remote task invocation, and encryption of client/server communication using TLS/SSL, as Technical Preview features in the Hot Rod C# client.
These enhancements are applicable to Client-Server mode.
Chapter 3. Deprecated or Removed Features
Copy linkLink copied to clipboard!
3.1. Deprecated or Removed Features
Copy linkLink copied to clipboard!
Red Hat JBoss Data Grid (JDG) 7.0 is a new release stream. Certain features from JDG 6.6 have been removed or deprecated in JDG 7.0. For the list of such features, please refer to the JDG 7.0 Migration Guide.
Chapter 4. Supported Configurations
Copy linkLink copied to clipboard!
4.1. Supported configurations
Copy linkLink copied to clipboard!
Supported hardware and software configurations for JDG 7.0 are available on the Customer Portal at https://access.redhat.com/articles/2435931.
Chapter 5. Component Versions
Copy linkLink copied to clipboard!
5.1. Component Versions
Copy linkLink copied to clipboard!
The full list of component versions used in Red Hat JBoss Data Grid is available at the Customer Portal at https://access.redhat.com/site/articles/488833.
Chapter 6. Known Issues
Copy linkLink copied to clipboard!
6.1. Known Issues
Copy linkLink copied to clipboard!
- JDG-435 - JDBC store configuration is not copied when creating new template from basic configuration
- When creating a new template the JDBC cache store configuration is not copied over, and must instead be manually entered.This is a known issue in JBoss Data Grid 7.0.0, and no workaround exists at this time.
- JDG-436 - JMX operation ClusterCacheStats.resetStatistics() not working
- When executing the JMX operation
ClusterCacheStats.resetStatistics()none of the cluster statistics are reset.This is a known issue in JBoss Data Grid 7.0.0, and to workaround this issue executeStatistics.resetStatistics()on each server individually. - JDG-474 - CLI - container and cache commands don't work in domain mode
- When executing
containerorcachebased commands through the CLI in domain mode the following message is displayed:Container does not exists
Container does not existsCopy to Clipboard Copied! Toggle word wrap Toggle overflow This is a known issue in JBoss Data Grid 7.0.0, and no workaround exists at this time. - JDG-477 - The C# client does not have asynchronous versions of cache operations
- Unlike the C++ and Java Hot Rod clients, the C# client does not include asynchronous versions of cache operations at this time.This is a known issue in JBoss Data Grid 7.0.0, and a workaround exists by using the Task API to wrap the cache operation. For instance, the following example demonstrates performing an asynchronous
Put(key, value):await Task.Run(() => cache.Put(k,v))
await Task.Run(() => cache.Put(k,v))Copy to Clipboard Copied! Toggle word wrap Toggle overflow - JDG-244 - Spark connector fails with CCE when compatibility mode is enabled
- When attempting to insert values into a cache using the Spark connector while compatibility mode is enabled the request will fail with a
ClassCastException.This is a known issue in JBoss Data Grid 7.0.0, and to workaround this issue disable compatibility mode. - JDG-333 - NotSerializableException while executing streams via JavaScript in a cluster in DIST mode
- It is not possible to use scripts that create a
Streamin JavaScript when the cluster is inDISTmode. Any attempts to execute these scripts will result in aNotSerializableException, as the lambdas fail when attempting to be serialized.This is a known issue in JBoss Data Grid 7.0.0, and to workaround this issue it is recommended to manually iterator over data using anIterator, or to execute lambdas after the data has been transferred from the script to the originator node. - JDG-96 - Cache events are incompatible with CDI 1.1 in JDG 7
- When using CDI annotations with the CDI 1.1 API, such as the version found within JBoss EAP 7, a java.lang.RuntimeException is thrown; this exception is thrown as the cache events used by JBoss Data Grid 7.0 include content that has been removed by CDI 1.1.This is a known issue in JBoss Data Grid 7.0.0. This issue is resolved in the CDI 1.2 API; to workaround this issue attach the listeners manually, as outlined in the following steps:
- Remove CDI annotations from the listener bean, including removing all
@Observesannotations from methods. - Add Listener annotations on desired methods; for example,
@CacheStarted. - Manually register listeners using
AdvancedCache#addListener.
- JDG-447 - Changing transport configuration results in restarting wrong cluster
- When updating one server group's transport configuration through the Administration Console and accepting the prompt to restart the server group remains running. Instead, a second server group is restarted in its place.This is a known issue in JBoss Data Grid 7.0.0, and no workaround exists at this time.
- JDG-448 - Endpoints column on cache container page shows wrong ports
- When examining the port for containers in the Administration Console the
port-offsetis not considered, causing multiple containers to show at the same port.This is a known issue in JBoss Data Grid 7.0.0, and no workaround exists at this time. - JGRP-2088 - ArrayIndexOutOfBoundsException on ClassConfigurator.get()
- When attempting to use the JGroups
ENCRYPTprotocol aArrayIndexOutOfBoundsExceptionis thrown.This is a known issue in JBoss Data Grid 7.0.0, and to workaround this issue use theSYM_ENCRYPTorASYM_ENCRYPTprotocols, as described in the JBoss Data Grid Administration and Configuration Guide.
Appendix A. Revision History
Copy linkLink copied to clipboard!
| Revision History | |||||
|---|---|---|---|---|---|
| Revision 7.0.0-3 | Sat 16 Jul 2016 | ||||
| |||||
| Revision 7.0.0-2 | Wed 27 Apr 2016 | ||||
| |||||
| Revision 7.0.0-1 | Wed 27 Apr 2016 | ||||
| |||||
| Revision 7.0.0-0 | Tue 5 Apr 2016 | ||||
| |||||
Legal Notice
Copy linkLink copied to clipboard!
Copyright © 2016 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}