Tuesday, 03 March 2020

Infinispan 11.0.0.Alpha2 and 10.1.3.Final

Dear Infinispan community,

we’ve just tagged a couple of releases.

First off is the second Alpha release of what will eventually become Infinispan 11. The release notes may not be exciting, but it is mostly preparatory work for the big features we are working on: vastly improved async cross-site replication, monitoring, query improvements, the console and the CLI, and more.

We also released a micro-update to 10.1 which fixes quite a few bugs, especially in the way we handle JMX and MP metrics and further improves the documentation.

New release naming scheme

Starting with the next development release of Infinispan 11, we will be adopting a new naming scheme. We will no longer be using the Alpha and Beta monikers, but we will use a progressive Dev suffix to indicate that it’s a development release. The next release will therefore be called 11.0.0.Dev03.

Get it, Use it, Ask us!

Please download, report bugs, chat with us, ask questions on StackOverflow.

Posted by Tristan Tarrant on 2020-03-03
Tags: release

Monday, 24 February 2020

Infinispan Operator 1.1.1 is out!

We’re pleased to announce version 1.1.1 of the Infinispan Operator for Kubernetes and OpenShift.

This release has focused on fixing bugs and improving robustness, mainly related to the following:

  • improving reconcile flow stability

  • reducing Operator CPU load

  • cleaning up logs

Our community documentation on https://infinispan.org/documentation has also been updated and improved. You can find some of the changes at:

Automatic Upgrades

If you installed the Infinispan Operator on Red Hat OpenShift with the Automatic Approval upgrade policy, your cluster should already be running the latest versions (Infinispan Operator 1.1.1 with Infinispan 10.1.2.Final).

We would like to hear opinions from you about the automated upgrade process, so get in touch if you have any issues or want to give any feedback.

Get it, Use it, Ask us!

Try the simple tutorial for the Operator, which has been updated for this version.

You can report bugs, chat with us, ask questions on StackOverflow.

Finally, a detailed list of issues and features for this version can be found here.

Posted by Vittorio Rigamonti on 2020-02-24
Tags: release operator

Monday, 10 February 2020

Infinispan Spring Boot Starter released with Spring Boot 2.2.4.RELEASE

Dear Infinispan and Spring Boot users,

We are pleased to announce the release of Infinispan Spring Boot  2.1.8.Final and 2.2.0.Final.

2.1.8.Final uses Infinispan 9.4.17.Final and Spring Boot 2.2.2.RELEASE

2.2.0.Final uses Infinispan 10.1.1.Final and Spring Boot 2.2.2.RELEASE 

Configuring Marshalling with Infinispan 10.x

Infinispan 10.x servers have some significant changes to marshalling that impact Spring Boot users.

The default Marshaller for Infinispan 10.x is ProtoStream, which uses Protocol Buffers to provide extensible, language and platform neutral serialization.

Unfortunately ProtoStream does not currently work with Infinispan Spring Cache and Session support. As a result, Spring users in Remote Client/Server Mode must use the Java Serialization Marshaller and add classes to a Java serialization whitelist.

Add the following configuration properties:

infinispan.remote.marshaller=org.infinispan.commons.marshall.JavaSerializationMarshaller infinispan.remote.java-serial-whitelist=org.infinispan.tutorial.simple.spring.remote.*

The infinispan.remote.java-serial-whitelist property specifies the classes, or packages, that Java serialization can marshall. Separate multiple class names with a comma (,).

Note that, in previous versions, JBoss Marshaller was the default for Infinispan. Spring users can also use JBoss Marshalling, but it is deprecated as of Infinispan 10.x.

Get it, Use it, Ask us!

You can find these releases in the maven central repository.

Please report any issues in our issue tracker and join the conversation in our Zulip Chat to shape up our next release.

Enjoy,

The Infinispan Team

Posted by Katia Aresti on 2020-02-10
Tags: release spring boot spring

Friday, 24 January 2020

Infinispan Operator 1.1.0 is out!

We’re pleased to announce version 1.1.0 of the Infinispan Operator for Kubernetes and OpenShift.

This release includes a bunch of very exciting features! Let’s dig into them:

Full Lifecycle

Infinispan Operator 1.1.0 is rated at the Full Lifecycle capacity level, which means the Operator now provides advanced cluster management capabilities and functionality to handle demanding workloads.

One of the key new features in this release is graceful shutdown, which lets you bring clusters down safely to avoid data loss.

During cluster shutdown, caches can passivate in-memory entries to persistent storage along with the internal Infinispan state that maps which nodes own which entries. When you bring Infinispan clusters back, all your data is restored to memory.

Check out the Graceful Shutdown docs for more information.

Graceful shutdown also enables the Infinispan Operator to perform reliable upgrades.

When a new version of the Infinispan Operator starts, it checks for running Infinispan clusters that were created by an older Operator version.

If the Operator detects a cluster that requires upgrade, it invokes a graceful shutdown on the cluster and then brings it back with the new Infinispan version.

You can perform upgrade manually or automatically with the Operator Lifecycle Manager on OpenShift.

Note that Operators installed via the OperatorHub on OpenShift Container Platform are managed by the Operator Lifecyle Manager.

Cache vs DataGrid

This version of the Infinispan Operator delivers Cache and DataGrid services.

By default the Operator starts Infinispan clusters as Cache services, which provides a quick way to set up in-memory caching that stores data off-heap and keeps single copies of data in the cluster.

DataGrid services, on the other hand, are suited to more advanced use cases where you control and define the configuration that you need.

Cross-Site Replication

The Infinispan Operator simplifies cross-site replication set up with DataGrid services so you can back data up between separate Kubernetes or OpenShift clusters.

All you need to do is specify which type of external Kubernetes service to expose, the list of all backup locations, access secrets, and the local site name.

Find out more at: Cross-Site Replication

Automatic TLS configuration

If you’re running on Openshift and have a service that serves certificates, the Operator automatically asks for certificates sets up TLS for your endpoint connections. Encrypted by default with zero effort!

Get it, Use it, Ask us!

Try the simple tutorial for the Operator, which has been updated for this version. The tutorial shows how to install the Operator manually, but it can also be installed via the Operator Hub on OpenShift.

You can report bugs, chat with us, ask questions on StackOverflow.

Finally, a detailed list of issues and features for this version can be found here.

Posted by Galder Zamarreño on 2020-01-24
Tags: release operator

Monday, 23 December 2019

Infinispan 10.1.0.Final

Hi there,

we finish 2019 in style with the Final release of Infinispan 10.1, codenamed "Turia".

Server console

The highlight of this release is the new server console which is now based on Patterfly 4 and React.js. We will soon have a blog post detailing the work that has been done and our future plans. In the meantime, here are a few screenshots:

Welcome Page
Console Caches
Console Cache Stats

Security

Many changes related to security have happened since 10.0:

  • Native SSL/TLS provided by WildFly OpenSSL. The server only ships with native libraries for Linux x86_64, but you can download natives for other platforms and architectures

  • Improved usability of the Hot Rod client configuration with better defaults

  • Full support for authorization for admin operations via the RESTful endpoint

  • Console authentication support

  • Kerberos authentication for both Hot Rod (GSSAPI, GS2) and HTTP/Rest (SPNEGO)

  • Improved LDAP realm configuration with connection tuning and attribute references

  • Rewritten client/server security documentation including examples on how to create certificate chains, connecting to various LDAP directories and KeyCloak, etc.

Server

  • A command-line switch to specify an alternate logging configuration file

  • Query and indexing operations/stats are now exposed over the RESTful API

  • Tasks and Scripting support

  • Support for binding the endpoints to 0.0.0.0 / ::0 (aka INADDR_ANY)

Non-blocking

More work has landed on the quest to completely remove blocking calls from our internals. The following have been made non-blocking:

  • State transfer

  • The size operation

  • Cache stream ops with primitive types

Additionally caches now have a reactive Publisher which is intended as a fully non-blocking approach to distributed operations.

Query

  • The query components have been reorganized so that they are more modular.

Monitoring

  • The introduction of histogram and timer metrics.

  • The /metrics endpoint now includes base and vendor microprofile metrics

Stores

  • The REST cache store has been updated to use the v2 RESTful API.

Removals and deprecations

  • The old RESTful API (v1) has been partially reinstated until 11.0. Bulk ops are disabled.

  • The Infinispan Lucene Directory has been deprecated.

  • The memcached protocol server has been deprecated. If you were relying on this, come and talk to us about working on a binary protocol implementation.

Bug fixes, clean-ups and documentation

Over 160 issues fixed including a lot of documentation updates. See the full list of changes and fixes

Get it, Use it, Ask us!

Please download, report bugs, chat with us, ask questions on StackOverflow.

Posted by Tristan Tarrant on 2019-12-23
Tags: release

Monday, 09 December 2019

Infinispan 10.1.0.CR1

Dear Infinispan community,

as we are closing in on 10.1, we have been working on a lot of polishing and bugfixing.

Server

  • The new console has received a lot of improvements,

  • A new welcome page

  • A command-line switch to specify an alternate logging configuration file

Query

The query components have been reorganized so that they are more modular.

Monitoring

  • The introduction of histogram and timer metrics.

Stores

  • The REST cache store has been updated to use the v2 RESTful API.

Removals and deprecations

  • The old RESTful API (v1) has been removed

  • The Infinispan Lucene Directory has been deprecated.

  • The memcached protocol server has been deprecated. If you were relying on this, come and talk to us about working on a binary protocol implementation.

Bug fixes, clean-ups and documentation

Over 40 issues fixed including a lot of documentation updates. See the full list of changes and fixes

Get it, Use it, Ask us!

Please download, report bugs, chat with us, ask questions on StackOverflow.

Infinispan 10.1.0.Final is scheduled for December the 20th.

Posted by Tristan Tarrant on 2019-12-09
Tags: release candidate release

Monday, 25 November 2019

Infinispan Operator 1.0.1

Dear Infinispan community,

we know you are happy with the new shining 10.0.0 Infinispan release, but if you are among those who are missing a new operator version for safely running your Infinispan Chupachabra in the clound, this post is for you!

Versioning and channels

This is our first blog post about 1.0.x operator series (yeah, sorry 1.0.0 we forgot about you) and as you can notice there’s no Alpha, Beta or CR label at the end of the release tag. This is because OperatorHub and Openshift Catalog only allow numerical version like Maj.Min.Mic and instead of labels we now use the channel to indicate the stability of a release. We have 2 live channels at the moment for the Infinispan operator: stable and dev-preview. Current stable is 0.3.2 which is for the 9.x Infinispan cluster and current dev-preview is 1.0.1 which works with 10.x clusters.

New features

  • New Infinispan image configuration: we cleaned up the image configuration process: instead of rely on a large set of env variables, now the operator configures the Infinispan image via a single .yaml file.

  • Container configurability: CR .yaml file lets you configure memory and CPU (and also extras Java opts) assigned to the container;

  • Encryption: TLS can be setup providing TLS certificates or using platform service as the Openshift seriving certs service (TLS will be on by default in the next release);

  • We now have some good docs: https://infinispan.org/infinispan-operator/master/operator.html;

  • Project README has been also improved: https://github.com/infinispan/infinispan-operator/blob/1.0.1/README.md;

Get it

The Infinispan Operator 1.0.1 works on Kind/Kubernetes 1.16 (CI) and Openshift 3.11, 4.x (developed on). You can install it:

And remember: it’s a dev-preview release, you can have a lot of fun with it!

Contribute

As usual source code is open at: https://github.com/infinispan/infinispan-operator. You can see what’s going on, comment the code or the new pull requests, ask for new features and also develop them!

Thanks for following us, Infinispan

Posted by Vittorio Rigamonti on 2019-11-25
Tags: dev-preview release

Monday, 18 November 2019

Infinispan 10.1.0.Beta1

Dear Infinispan community,

Quick on the heels of Infinispan 10.0 here comes the first Beta or 10.1.

Server

This release closes the gap between the legacy server and the new server we introduced in 10.0. In particular:

  • The reworked console (which will be described in detail in an upcoming series of blog posts)

  • Kerberos authentication for both Hot Rod (GSSAPI, GS2) and HTTP/Rest (SPNEGO)

  • Query and indexing operations/stats are now exposed over the RESTful API

  • Tasks and Scripting support

Non-blocking

More work has landed on the quest to completely remove blocking calls from our internals. The following have been made non-blocking:

  • the size operation

  • cache stream ops with primitive types

Additionally caches now have a reactive Publisher which is intended as a fully non-blocking approach to distributed operations.

Components upgrades

  • rxjava 2.2.12

  • smallrye metrics 2.3.0

  • microprofile metrics 2.2

Bug fixes, clean-ups and documentation

Over 40 bug fixes. See the full list of changes and fixes

Get it, Use it, Ask us!

Please download, report bugs, chat with us, ask questions on StackOverflow.

Infinispan 10.1.0.CR1 is scheduled for December the 7th.

Posted by Tristan Tarrant on 2019-11-18
Tags: beta release

Friday, 01 November 2019

Infinispan 10.0.1.Final

We are pleased to announce the availability of Infinispan 10.0.1.Final, which contains several bug fixes.

The release notes can be found here.

As usual you can ask questions on the forum, StackOverflow and interactively on our Zulip Chat. Please report any bugs you find on our Issue Tracker

Posted by Ryan Emerson on 2019-11-01
Tags: final release

Monday, 28 October 2019

Infinispan 10.0.0.Final

Dear Infinispan community,

We are very pleased to announce the release of Infinispan 10.0 codenamed “Chupacabra”! We have been busy making many changes over the last months.

Server

Infinispan 10 features a brand new server, replacing the WildFly-based server we’ve had since 5.3 with a smaller, leaner implementation. Here are the highlights:

  • Reduced disk (50MB vs 170MB) and memory footprint (18MB vs 40MB at boot)

  • Simpler to configure, since it shares the configuration schema with embedded with server-specific extensions

  • Single-port design: the Hot Rod, REST and management endpoint are now served through a single port (11222) with automatic protocol detection between HTTP/1.1, HTTP/2 and Hot Rod. The memcached endpoint is handled separately since we don’t implement the binary protocol yet.

  • New CLI with data manipulation operations

  • New REST-based API for administration

  • Security implemented using WildFly Elytron:

  • Hot Rod authentication support for PLAIN, DIGEST-MD5, SCRAM, EXTERNAL, OAUTHBEARER

  • HTTP authentication support for BASIC, DIGEST, CLIENT_CERT and TOKEN

  • Properties, Certificate Store and LDAP realms

  • Integration with KeyCloak

  • Caches/counters are created and managed dynamically through Hot Rod / REST

Because of the amount of restructuring, the web-based Console is not yet available in this release. We are working on it and it will be included in 10.1.

REST Endpoint

A new API (v2) was introduced and users are encouraged to migrate their applications from the old API.

The v2 API offers a completely redesigned endpoint, including dozens of new operations. Besides allowing to manage caches, it also covers cache containers, counters, cross-site replication, servers and clusters.

Apart from the new API, the REST server is now fully non-blocking and also has better performance than 9.4.x. It also fully supports authorization.

Marshalling

The internal marshalling capabilities of Infinispan have undergone a significant refactoring in 10.0. The marshalling of internal Infinispan objects and user objects are now truly isolated. This means that it’s now possible to configure Marshaller implementations in embedded mode or on the server, without having to handle the marshalling of Infinispan internal classes. Consequently, it’s possible to easily change the marshaller implementation user for user types, in a similar manner to how users of the HotRod client are accustomed.

As a consequence of the above changes, the default marshaller used for marshalling user types is no longer based upon JBoss Marshalling. Instead we now utilise the ProtoStream library to store user types in the language agnostic Protocol Buffers format. The ProtoStream library provides several advantages over jboss-marshalling, most notably it does not make use of reflection and so is more suitable for use in AOT environments such as Quarkus.

Persistence

The persistence SPI has had some much needed TLC, with several deprecations and additions. The aim of this work was to ensure that internal Infinispan classes were no longer leaking into the SPI, in order to ensure that custom store implementations only have to be concerned with their data, not internal Infinispan objects.

Stores by default are now segmented when the segmented attribute is not set. A segmented store allows for greater iteration performance and less memory usage. This is useful for things such as state transfer and other operations that require an entire view of the cache (iteration, size, mass indexer distributed streams etc). All of our provided stores now provided being segmented; these include file store, soft index file store, rocks db, jdbc and remote stores.

Container Image

To accommodate our brand new server, Infinispan 10.0 also introduces a completely new container image which is much smaller than the old one (366MB vs 684MB) and supports the following features:

  • Red Hat’s Minimal Universal Base Image based

  • Java 11

  • Simple yaml configuration

  • Authentication (Enabled by default)

  • Encryption

  • Logging

  • XSite support

The new image can be pulled from any of the following repositories:

Metrics and Logging

Infinispan has adopted the MicroProfile Metrics ver. 2.0.2 specification and uses the SmallRye Metrics implementation. MicroProfile Metrics allows applications to gather various metrics and statistics that provide insights into what is happening inside an Infinispan cluster.

The current offering includes both cache container and cache level Gauge type metrics. Histograms and Timers will arrive in the next release of the 10.x stream.

The metrics can be read remotely at the well-known /metrics REST endpoint and use JSON format or optionally the OpenMetrics format, so that they can be processed, stored, visualized and analyzed by compatible tools such as Prometheus.

But rest assured, the existing JMX support for metrics has not been superseded by REST. JMX is still alive and kicking and we plan to continue developing it and have it available on all runtimes that support it (Quarkus being the notable exception).

Logging categories for the major subsystems have been introduced (CLUSTER, CONTAINER, PERSISTENCE, SERVER, etc) so that it easier to understand what they refer to. The server also comes with a JSON logger for easy integration with tools such as Fluentd or the ELK stack.

Quarkus

Infinispan is an official extension in Quarkus! If you wish to find out more about Quarkus you can find it at https://quarkus.io/.

We have a very featureful client extension allowing your Quarkus apps to connect to a remote server with lots of the features you are used to: querying, authentication, encryption, counter, dependency injection and others. We recently added support for protostream based annotation marshalling. If you are curious you can find the code at https://github.com/quarkusio/quarkus/tree/master/extensions/infinispan-client.

The Infinispan embedded extension was also just added, but has limited functionality due to its infancy. Although it will allow you to run an embedded clustered cache in a native executable. If you are curious you can find the code at https://github.com/quarkusio/quarkus/tree/master/extensions/infinispan-embedded.

The Infinispan team has also started adding a standalone project to have a Quarkus based Infinispan Server using Infinispan 10 and newer. This is still a work in progress, but the new repository can be found at https://github.com/infinispan/infinispan-quarkus-server.

Quarkus has a different release cycle than Infinispan, so watch out for more improvements over the following weeks !

Cross-Site Replication

Async mode cross-site replication received 3 major improvements: Concurrent requests (i.e. write on different keys for example) will be handled simultaneously instead of sequentially. Asynchronous mode is now able to detect disconnections between sites and bring the site offline based on <take-offline> configuration (ISPN-10180) Tracks and exposes some metrics for asynchronous requests (ISPN-9457)

Internals

Dependency Injection

Infinispan’s internal dependency-injection has been completely rewritten so that factories, components and dependencies are discovered and resolved at compile time instead of using runtime reflection. This, together with the marshalling changes and recent JGroups changes, paves the way for usage and native compilation with Quarkus.

Non-blocking

Several internal subsystems have been rewritten to be non-blocking, meaning that they will not hold-on to threads while waiting for I/O:

  • Non-blocking Hot Rod authentication (ISPN-9841)

  • Non-blocking REST endpoint (ISPN-10210)

  • Update internal remote listener code to support non blocking (ISPN-9716)

  • Update internal embedded listeners to be non blocking (ISPN-9715)

  • Passivation throughput is increased as well as these operations are done asynchronously.

  • In addition cache stores have been made non blocking for the cases of loading an entry and storing into the data container as well write skew checks. With this we should be at a point where we can start consolidating thread pools, so keep a look-out in the upcoming releases.

  • Distributed Streams utilizing a terminal operator that returns a single value use non blocking communication methods (ISPN-9813)

Off Heap Storage Improvements

Off Heap has added a few improvements to increase performance and reduce memory usage.

  • Iteration imrpovements (ISPN-10574)

    • Removes the need for the address count configuration option

    • Dynamically resize underlying bucket

    • Reorder bucket iteration to more CPU friendly, less lock acquisiations as well

  • StampedLock instead of ReadWriteLock (ISPN-10681)

Expiration Improvements

Cluster Expiration has been improved to only expire entries on the primary node to reduce the amount of concurrent expirations from multiple nodes in the cluster. Also the amount of concurrent expirations on a single node has been improved for better handling.

Additionally, expirations are not replicated cross site to reduce chattiness on the cross site link. Also to note that lifespan works fine without this and max-idle expiration does not work properly with cross site. So in this case the messages were providing no benefit.

API

We now have a proper sizeAsync method on the Cache interface. This is both for remote and embedded APIs. This method should be preferred over the current size due to not blocking the invoking thread as well as being able to retrieve the size as a long instead of a int.

Configuration

It is now possible to configure JGroups stacks directly from the Infinispan configuration file. We use this ability to also allow easily creating multiple stacks (for easy cross-site configuration). The distribution comes with several pre-built JGroups stacks for cloud environments which you can quickly adapt for your configuration. Additionally you can extend existing JGroups configurations replacing individual protocols. This makes it easy, for example, to use a different discovery without worrying about all the other protocols.

Documentation

Infinispan community documentation has been going through some big changes over the past year. The Infinispan 10 release marks the first major step towards adopting a modular structure that supports flexible content for specific use cases. On top of that we’ve also been putting lots of effort into transforming our documentation set to adhere to the principles of minimalism that put focus on user goals and delivering leaner, more concise content.

Our 10.0 release also incorporates work to organize content into three main types: task, concept, and reference. Mapping content to information types makes it easier to write and maintain content by removing worries about style, scope, and other complexities. Writers can separate documentation into logical units of information that can stand alone and then assemble topics into tutorials, how-to articles, explanations, and reference material.

You might also notice some changes to the documentation section of our site and updates to the index page for Infinispan 10 docs. Hopefully the new layout makes it easier to navigate and find the information you’re looking for.

We hope you find the improvements to the documentation helpful. As always, we’re keen to get your feedback and would appreciate. And if you feel like getting involved, see the Contributor’s Guide and start writing Infinispan docs today!

Experimental features

Reactive API

First steps to a new Reactive API. This is still a work in progress and the API will see major changes. We plan on making this API final and default in Infinispan 11. The new API includes a new API module and a new KeyValueStore Hot Rod client where search, continuous search and Key Value store methods are included

Removal/deprecations

A new major release is also an opportunity to do some house-cleaning.

Deprecations

  • Deprecate GridFileSystem and org.infinispan.io stream implementations (ISPN-10298)

  • Deprecated Total Order transaction mode (ISPN-10259)

  • Deprecated Externalizer, AdvancedExternalizer and @SerializeWith (ISPN-10280)

Removals

  • AtomicMap implementations (ISPN-10230)

  • Deprecated org.infinispan.io classes (ISPN-10297)

  • org.infinispan.tools.ConfigurationConverter (ISPN-10231)

  • Compatibility mode (ISPN-10370)

  • AtomicObjectFactory (ISPN-10414)

  • C3P0 and Hikari Connection Pools (ISPN-8087)

  • Delta and DeltaAware interfaces (ISPN-8071)

  • HotRod 1.x support (ISPN-9169)

  • Tree module (ISPN-10054)

  • Distributed Executor (ISPN-9784)

Get it, Use it, Ask us!

Please download, report bugs, chat with us, ask questions on StackOverflow.

Future

Now that Infinispan 10 is out we plan on delivering a 10.1 release in a couple of months. 10.1 will generally be a polishing release.

Posted by Tristan Tarrant on 2019-10-28
Tags: final release
back to top