Friday, 01 November 2019
Tags: final release
Monday, 28 October 2019
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.
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.
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.
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.
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.
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
Simple yaml configuration
Authentication (Enabled by default)
The new image can be pulled from any of the following repositories:
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.
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 !
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)
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.
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 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)
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.
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.
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.
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!
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
A new major release is also an opportunity to do some house-cleaning.
Deprecate GridFileSystem and org.infinispan.io stream implementations (ISPN-10298)
Deprecated Total Order transaction mode (ISPN-10259)
Deprecated Externalizer, AdvancedExternalizer and @SerializeWith (ISPN-10280)
AtomicMap implementations (ISPN-10230)
Deprecated org.infinispan.io classes (ISPN-10297)
Compatibility mode (ISPN-10370)
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)
Tags: final release
Thursday, 21 February 2019
Hello Infinispan users,
What ? You’re wondering where Beta1 is ? And what happened to 9.4.7 ? Unfortunately, those releases, while tagged and available on your closest Maven Central mirror will only work with Java 11, so we had to rebuild and re-release.
So, without further ado, I give you 10.0.0.Beta2 and 9.4.8.Final.
The first change I should outline is one that will impact you if you are building Infinispan from source. The previous build structure required having both JDK 8 and JDK 11 in order to compile a release which worked on both. In order to simplify the build process, as well as ensuring that the output is always consistent we now require Java 11 only. Don’t worry: the resulting binaries will still work on Java 8 and greater.
The first beta of our next major release contains a number of enhancements:
We will soon be posting about these features individually.
The work on persistent storage long-term compatibility is progressing with [ISPN-9845] - Stop exposing InternalMetadata via the persistence SPI
[ISPN-4075] - State transfer should preserve the creation timestamp of entries
And if you were still using the old Distributed Executor, that has been finally removed in [ISPN-9784] - Remove Distributed Executor
Tags: beta release final
Wednesday, 21 November 2018
Today we are releasing 10.0.0.Alpha1 and 9.4.2.Final.
Infinispan 9.4.2.Final comes with a number of bug fixes and some small additional features:
We have begun working on what will become Infinispan 10. As with all new major releases, this will come with a number of important changes.
New Server We are working on a new lightweight server, currently dubbed ServerNG, which will supersede the current WildFly-based offering. The new server will have a smaller disk and memory footprint, a new RESTful admin interface, improved security. It will still use familiar components (Elytron for security, Narayana for transactions, etc) but we hope that the installation and usability experience will be most improved. A dedicated blog post will describe in detail what is coming.
Long-term Storage Format The persistent storage format will be changed so that it will be easier to transparently make changes to it without requiring further exporters/importers.
Non-blocking listeners The listener implementation will be replaced with a non-blocking implementation.
Asynchronous CacheLoader/Store Store operations will be ran in another thread to provide non blocking for main threads
Improved statistics Infinispan statistics have been traditionally over-simplistic, offering mostly basic averages for writes and reads. We are going to implement percentiles on a histogram as well as recording tracing information so that you will be able to know how much time is being spent in the various subsystems (clustering, persistence, etc.)
New API The current Infinispan API, based around Java’s ConcurrentHashMap design, does not offer the flexibility required to support modern reactive designs as well as the various extensions we’ve added over the years (counters, multimaps, etc). We are therefore working on a new modern API design which we will be describing with a number of blog posts in the near future.
Agroal JDBC Connection Pool We are replacing the JDBC connection pool implementation with Agroal.
Kubernetes Operators Operators are all the rage in the Kubernetes world, and we are working on an Infinispan Operator which will take care of managing and monitoring the health of an Infinispan cluster, handle scale up/scale down safely, perform upgrades and more.
Infinispan 10.0.0.Alpha1 is the first release from our development branch. It currently includes the following features on top of what is in 9.4.2.Final:
Tags: release final alpha roadmap
Thursday, 15 November 2018
The C++ and C# 8.3.0.Final releases are out!
Main features contained in this release are:
Cache Admin Operations: create and remove cache at runtime;
Counters: clusterwide counters;
Transactions: run a list of operations transactionally;
Media Types: use differents media-types to encode (key,value) pairs.
Source code, binaries and docs are available as usual at the links below.
Thank you for reading, The Infinispan Team
Tags: c++ release final c#
Thursday, 30 August 2018
Dear Infinispan users,
We have just released 9.3.2.Final and 9.4.0.CR2.
9.3.2.Final includes bug fixes and improvements.
Highlights of this release include:
The full list of 9.3.2.Final fixes are here.
9.4.0.CR2 has been released due to an internal issue we experienced releasing CR1.
The Infinispan Team
Tags: release final release candidate
Tuesday, 26 June 2018
We’re delighted to announce the release of Infinispan 9.3.0.Final, which is a culmination of several months of hard work by the entire Infinispan community. Here’s a summary of what you can find within it:
First final release to work with both Java 8 and Java 10. Note that Infinispan only works in classpath mode.
Transaction support Hot Rod. The java Hot Rod client can participate in Java transactions via Synchronization or XA enlistment. Note that recovery isn’t supported yet.
Caches can now configure the maximum number of attempts to start a CacheWriter/CacheLoader on startup before cache creation fails.
Write-behind stores are now fault-tolerant by default.
Segmented On Heap Data Container. It improves performance of stream operations.
Server upgraded to Wildfly 13.
We have introduced several WildFly feature packs to make it easier for Infinispan to be utilised on WildFly instances via the Server Provisioning Plugin. The following feature packs have been created, most notably:
All of the modules required to connect to a hotrod server via the client
The modules required for embedded instances of Infinispan
The same as above but with query capabilities
This is equivalent to the Wildfly-modules.zip
Hibernate second-level cache provider works with Hibernate ORM 5.3.
The Hot Rod Server allows now to use multiple protocols with a Single Port. The initial version supports HTTP/1.1, HTTP/2 and Hot Rod. Switching protocols can be done using TLS/ALPN and HTTP/1.1 Upgrade header.
Admin console - improved all editors (schema, scripts, JSON data) to include syntax highlighting.
Several enhancements in the Java Hot Rod client allowing to read and write data in different formats such as JSON, for cache operations and deployed filters/converters.
Cluster wide max idle expiration.
Hibernate Search 5.10
Hibernate ORM 5.3
Numerous bug fixes which improve stability
For more details, please check our issue tracking release notes.
Thanks to everyone involved in this release! Onward to Infinispan 9.4!
Tags: release final
Wednesday, 02 May 2018
We have two releases to announce:
Next is 9.3.0.Alpha1 which is the first iteration of our next release. The main item here, aside from bugfixes and preparation work for upcoming features, is the upgrade of our server component to WildFly 12.
Go and get them on our download page
Tags: release final alpha hibernate second level cache provider
Tuesday, 13 March 2018
We’re pleased to announce the availability of the 8.2.0.Final release of the C++ and C# Hotrod clients. Here is what happened in the 8.2.0 episode:
SASL: PLAIN, MD5, EXTERNAL, GSSAPI (linux only)
simplified remote exec API
SASL: PLAIN, MD5, EXTERNAL
simplified remote exec API
You can find more info and even the binaries at the usual places
In the backstage people are already working on the 8.3.0 episode, you can partecipate expressing your opinion or adding your ideas here .
Thank you for reading.
The Infinispan Team
Tags: c++ release final c#
Friday, 14 July 2017
Dear Infinispan users,
after 3½ months, we are proud to present to you our latest stable release, Infinispan 9.1, codenamed "https://revbrew.com/beer/archive/bastille[Bastille]".
While minor releases are traditionally evolutionary instead of revolutionary, this release still comes loaded with a number of great features:
A new clustered cache, similar to a distributed cache, but with a higher write throughput.
An overhaul to partition handling which allows much finer control about whether to allow reads and writes in split clusters and how data is reconciled when partitions are merged.
An implementation of clustered counters with both strong and weak semantics, threshold events, optional persistence and bounding. Currently these are only available in embedded mode, but they will be usable over Hot Rod in Infinispan 9.2.
Locked streams allow you to run your stream processing operations knowing that another update cannot be performed while the Consumer is executed on an entry. Note this only works in non transactional and pessimistic transactional caches (optimistic transactional caches are not supported).
The compute(), computeIfPresent() and computeIfAbsent() methods on the Cache interface are now implemented as proper distributed operations so that they run local to the entries. The DeltaAware interface for supporting granular clustered operations has been deprecated in favour of functional commands.
The CacheStore SPI now supports write batching. The JDBC, JPA, RocksDB, Remote and File stores have been modified to take advantage of this. You should see great benefits when using write-behind or when using putAll operations.
Remote query now also works with Java entities annotated with Hibernate Search annotations and JBoss Marshalling without requiring ProtoBuf.
The REST endpoint has been completely rewritten so that it now supports both HTTP/1.1 and HTTP/2 as well as ALPN (even on Java 8). The new endpoint is also 30% faster during reads and 6% faster during writes.
The Java Hot Rod client now has proper entrySet(), keySet() and values() implementations which iterate over the remote data instead of pulling it all locally. It is now also finally possible to create and remove caches directly from the client.
The console has received a number of updates for usability and consistency. It is also finally possible to configure and manage the remote endpoints.
We have also dropped the guillotine on a large number of bugs.
If all goes well, we plan to release Infinispan 9.2 at the end of October, with lots of great updates.
The Infinispan team
Tags: release final