See Configuring Cross-Site Replication on OpenShift.

Find out complete details and learn how Data Grid detects and resolves conflicts in the documentation.

See Concurrent Writes and Conflicting Entries.

As of 8.1, you can set multiple site masters in your RELAY2 configuration to balance inter-cluster traffic. Use the max_site_masters attribute as in the following example:

<relay.RELAY2 site="NYC" 1
              max_site_masters="100"/> 2

See Setting Up Cross-Site Replication.

Data Grid Server 8.1 offers enhanced security and new configuration options.

See Adding Data Grid Credentials to create usernames and passwords for accessing the Data Grid Console, Command Line Interface (CLI), REST API, or Hot Rod endpoint.

See Securing Access to Data Grid Servers to learn about configuring different authentication mechanisms.

See Configuring Data Grid Server Data Sources.

<infinispan>
   <cache-container name="default">
      <security>
         <authorization> 1
            <identity-role-mapper/>
            <role name="AdminRole" permissions="ALL"/>
            <role name="ReaderRole" permissions="READ"/>
            <role name="WriterRole" permissions="WRITE"/>
            <role name="SupervisorRole" permissions="READ WRITE EXEC BULK_READ"/>
         </authorization>
      </security>
      <distributed-cache name="secured">
         <security>
            <authorization/> 2
         </security>
      </distributed-cache>
   </cache-container>
   ...
</infinispan>

See Configuring Data Grid Authorization.

Data Grid Operator 8.1 provides new features and improvements for running Data Grid on Red Hat OpenShift.

See Cross-Site Replication with Data Grid Operator.

See Exposing Data Grid Through Routes.

See Configuring Automatic Scaling.

See Securing Data Grid Connections.

See Creating Data Grid Caches.

Data Grid 8.1 CLI provides additional capabilities for server configuration, user management, and troubleshooting.

The user command lets you manage user credentials and groups for property-based security realms. For example, the following commands adds credentials that have "admin" privileges:

[disconnected]> user create myusername --password=qwer1234! --groups=admin

See Adding Data Grid Credentials.

[hostname@cluster//containers/default]> logging set --level=DEBUG org.infinispan

See Changing Data Grid Server Logging Configuration at Runtime.

Use the report command with the CLI as in the following example:

[hostname@cluster//containers/default]> server report
Downloaded report 'infinispan-hostname-timestamp-report.tar.gz'

See Getting Diagnostic Reports for Data Grid Servers.

Data Grid 8.1 Console provides additional capabilities such as:

For information on accessing the Data Grid Console and creating caches, see Creating Caches with the Data Grid Console.

hotrod[s]://[user[:password]@]host[:port][,host2[:port]][?property=value[&property2=value2]]

This provides a more compact way for configuring your Hot Rod Java client connections. See Hot Rod Client Configuration.

See Creating Caches on First Access.

Data Grid indexing and querying capabilities have undergone changes that decrease configuration overhead and offer better performance when searching the data store.

Major changes include:

Data Grid no longer supports native objects for Apache Lucene and Hibernate Search. Use the org.infinispan.query.Search class as your entry point for string-based searches with the Ickle query language.

See the following:

Data Grid 8.1 deprecates several configuration attributes to streamline user options and improve consistency between declarative and programmatic settings.

memory configuration is the most notable change in Data Grid 8.1. It lets you configure the data container to:

As in previous releases, the memory configuration can also configure Data Grid to store entries in binary format. However, as of 8.1, binary storage configuration is deprecated. Instead you should define the encoding for caches. If you want to use binary storage, specify the MediaType for any binary format in your cache definition.

See the following:

Data Grid consolidates thread pools into two:

As of this release, nearly all Data Grid internal components use the non- blocking thread pool, which increases throughput, reduces latency, and improves overall responsiveness for heavy I/O workloads.

Any blocking I/O paths, now use the blocking thread pool to avoid holding up non-blocking calls.

To handle blocking operations, Data Grid provides a BlockingManager utility class.

See the following:

Data Grid Modules for Red Hat JBoss EAP provide a temporary solution until planned functionality for Red Hat JBoss EAP to directly manage the infinispan subsystem is available.

See Data Grid Modules for Red Hat JBoss EAP.

You can find the complete list of issues for Data Grid with the following Jira query:

Query JQL

project = JDG AND affectedVersion in ("RHDG 8.1 CD", "RHDG 8.1 CR1", "RHDG 8.1 CR2", "RHDG 8.1 GA") AND status not in (Closed, Verified, "Ready for QA", "QA In Progress", Resolved) AND type = Bug

To configure Hot Rod clients, specify properties without the infinispan.client.hotrod. prefix. For more information, see the Hot Rod Client Configuration API.

You can also specify common attributes for the Session Manager. Refer to the appropriate version of the Apache Tomcat documentation as follows: