Monday, 15 July 2019

Infinispan 10.0.0.Beta4

Dear Infinispan users,

it has been a while since our last release and quite a few things have been cooking in the Infinispan furnace. Bear in mind that the list below should just serve as a summary and that dedicated blogs, documentation and examples will appear in the near future.

Server

Since 5.3, our server has been built on top of WildFly (JBoss AS7 at the time). WildFly gave us a very solid base, including integration with a lot of useful components (security, datasources, management etc) but it also forced us to maintain a large amount of integration code. We have therefore decided to start from a much leaner base to build the new server which, internally we've been calling ServerNG, but which we're now releasing as "Infinispan Server". The old WildFly-based server is still available, but it should be considered "legacy" and will no longer receive any feature enhancements.

The new server deserves its own dedicated post, but its main features are:
  • smaller size (36MB vs 130MB)
  • smaller memory footprint (20MB heap usage at boot vs 40MB)
  • single-port: 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.
  • security implemented using WildFly Elytron currently supporting PLAIN, DIGEST-MD5, SCRAM, EXTERNAL mechs for Hot Rod, BASIC, DIGEST, CLIENT_CERT for REST/HTTP (OAuth/JWT/GS2/GSSAPI/SPNEGO will be coming in the next releases)
  • the server configuration extends the embedded configuration scheme
  • caches/counters are created and managed dynamically through Hot Rod / REST.

Marshalling

Infinispan's marshalling has received a significant overhaul and it is now split into three distinct marshallers: Internal, Persistence and User (ISPN-7409 ISPN-9621)
The Persistence marshaller is now based on ProtoBuf allowing for long-term compatibility of data stored in memory and in cache stores.
The Store Migrator has been updated to allow migration from Infinispan 8.x/9.x cache stores to the new format (ISPN-10276)

Core changes

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.

REST

The REST API is continuing its overhaul with the following additions to the v2 API
The REST endpoint now fully supports authorization (ISPN-8736)

Reactive API

The first implementation of our new Reactive API have been merged. This is still work in progress and the API will receive major changes until the Final release.
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.

Cross-Site Replication

Async mode cross-site replication received 2 major improvements:
  • async mode is now able to detect disconnections between sites and bring the site offline based on <take-offline> configuration (ISPN-10180)
  • track and exposes the average replication times for asynchronous requests (ISPN-9457)

Non-blocking


  • 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)

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)

Removals

  • AtomicMap implementations removed (ISPN-10230)
  • Remove deprecated org.infinispan.io classes (ISPN-10297)
  • Remove org.infinispan.tools.ConfigurationConverter (ISPN-10231)
  • Remove compatibility mode (ISPN-10370)

If you are curious you can read the detailed release notes including all fixed issues.
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.
Going back to our three-week schedule, our next release will be Beta5, three weeks from now.

Friday, 12 July 2019

Infinispan Operator 0.3.0 expands container and security configuration!

Infinispan Operator 0.3.0 is now available with expanded configuration and security options:

Container Configuration


With this release of the Infinispan Operator, you can configure explicit CPU and memory limits for individual containers. The defaults are 0.5 CPUs and 512Mi of memory.

The Operator also lets you pass extra JVM options, which is useful for tracking native memory consumption or extra GC logging parameters.


Security Configuration


Starting with 0.3.0, credentials are automatically generated for data connector and management users when you instantiate the Infinispan Operator.

The default usernames are developer and admin for the data connector user and management user, respectively.

Generated passwords are stored in Kubernetes Secret instances. You can extract the passwords as follows:

For convenience, the default usernames are also stored in the secret. Using the jq command line tool, you can inspect both the username and password values with a single command:

If you want to set custom credentials for the data connector and management users, create Kubernetes Secret instances as follows:

When using a Credentials type authentication, the referenced secrets must contain username and password fields.

Trying It Out!


The easiest way to get started with the Infinispan Operator is via the simple tutorial. The Operator is compatible with vanilla Kubernetes environments, such as Minikube, as well as Red Hat OpenShift.

Available via Operator Hub


Install the Infinispan Operator directly from the Operator Hub, which is available out of the box on all OpenShift 4 versions. If you're using a vanilla Kubernertes environment, you might need to install the Operator Lifecycle Manager before you can install via the Operator Hub.

The Infinispan Operator is also included in the community for Kubernetes Operators is available from operatorhub.io.

What's Next?


The Operator configuration does not yet provide all capabilities available for Infinispan servers. We're working through a process of configuration specification that distills the server configuration into a simple, easy to use, set of configuration options. The current proposal is being discussed openly here.

Infinispan 10 brings a brand new server that's no longer based on WildFly. The Operator 0.x series will remain focused on Infinispan 9.x server, with Operator 1.x series focusing on Infinispan 10 and onwards.

Cheers,
Galder

Monday, 15 April 2019

Infinispan on tour, March-April 2019


Infinispan has been on tour!!

 I - Katia Aresti - had the chance to present 3 talks in 3 different conferences and countries during the last month:

Breizh Camp 2019 the 22th March, Rennes (France)

BreizhCamp - 9ème édition - 20, 21 et 22 Mars 2019 logo


Greach Conf 2019, 29th March, Madrid (Spain)

Greach 2019

Voxxed Days Milano 2019, 13th April, Milan (Italy)

VoxxedDays Milan


Breizh Camp

2019 has been BreizhCamp's 9th - Code Busters - edition and they sold-out the conference in a matter of hours (wow).

I did not have the time to attend any talk. Unfortunately, due to my personal schedule, I arrived on Thursday night, and I was presenting on Friday after lunch. This was the second time I was giving this presentation, but I did lot's of changes since the first time, including:

Breizh Camp Code Busters Edition, Photo credit @BreizhCamp 2019


On Friday morning I was stressed and I ran my presentation at the hotel. I arrived at the venue, delivered my talk and headed back to Paris. I deeply regretted not spending more time hanging out with other speakers and attendees, but I really couldn't make it this time :(

Greach Conf

Greach Conf is a lovely conference held in Madrid (Spain) for several years now. A 100% international conference, it has been organized by the Groovy community. 
This year they have changed the conference lineup adding an Android/Testing track and focusing on a bigger spectrum of technologies around the JVM.


Greach Conf 2019. Photo credit José Miguel Rodríguez


I learned a bunch of new things, including content related to SDKMan!, Gradle, the future of Grails and of course, Micronaut. As the principal maintainer of Spring-Boot and Infinispan integration, Micronaut felt new and familiar at the same time. I really enjoyed the workshop delivered by Alvaro Sánchez who will be in Devoxx France this week. The framework is really impressive. Give it a try!

You will find on Twitter a complete thread about my Greach Conf impressions:

Voxxed Days Milano

Voxxed Days Milano (Italy) was organizing the first edition this year and I really loved this conference in every aspect of it! Thanks, Mario Fusco and all the team involved for making it possible!

Voxxed Days Milano - Photo credit Sanne Grinovero 


I've written a full thread on Twitter with my impressions. You can find it attached to the tweet where I share all the content I've used in Greach Conf, BreizhCamp and Voxxed Days Milano:


Thanks to Breizh Camp, Greach Conf and Voxxed Days Milano for the opportunity to share around distributed caches and for the amazing time I've had during this month in each of the conferences.

This tour is now over for a while but will continue before summer. I will be presenting this talk (with upgrades, so stay tuned) in Dev Fest Lille in June 2019 (France), in Comunidad CODE (Virtual talk) and Software Crafters Bilbao in Spanish.

Devoxx France 

Devoxx France is taking place this week in Paris. I will be there, so if you want to chat about Distributed caches, Datagrids, NoSQL Key-Value databases, or integration with your favorite framework feel free to reach me on twitter!


There are lot's of new features and Reactive APIs to be done for Infinispan 10, so my main focus will be there for a bit.


Stay Tuned And Happy Coding!


Monday, 8 April 2019

Operator 0.2.1 out with DNS ping and expanded customizations

We've just completed the release of the Infinispan Operator version 0.2.1. In this second minor release, we've added the following features:

DNS Cluster Discovery


Cluster nodes now discover each other using DNS ping, which uses name lookups. Each node publishes a headless service which they use to locate each other. Previously, Kubernetes APIs were queried to discover other nodes, but this required administrator rights. DNS ping does not require admin permissions.

Configurable Image


The Infinispan server image used by the operator is now configurable, e.g.


Configurable XML


You can now provide their own custom Infinispan server XML referencing an existing ConfigMap:

Note that this example requires a ConfigMap with the XML file to be created before hand.

Next Steps


We're already working on version 0.3.0, and in parallel we've been working on our first OperatorHub submission. We hope to have some news for you very soon :)

Cheers,
Galder

Friday, 5 April 2019

Infinispan Spring Boot Starter 2.1.5.Final and 1.0.7.Final are out!


Dear Infinispan and Spring Boot users,

We have just released Infinispan Spring Boot Starter 2.1.5.Final and 1.0.7.Final.

2.1.5.Final


2.1.5.Final is using Infinispan 9.4.11.Final and Spring-Boot 2.1.4.RELEASE.

Important Spring-Boot bug fix

Previous versions of Spring-Boot 2.1.x contained a bug related to the multi-release jars. Infinispan contains multi-release jars, in consequence, we could not run our applications using java -jar with Java 11 (Java 8 worked fine). For additional explanations, read here.
Spring-Boot team has fixed this bug and released the correction in Spring-Boot 2.1.4.RELEASE, along with many other features and bug fixes, so consider upgrading soon.

Statistics on Client/Server mode and Actuator

Statistics configuration in client/server mode for the client evolved in the latest Infinispan versions. As a remainder, to activate actuator statistics in client/server mode :
- Configure 'infinispan.remote.statistics=true' in the application.properties
or
- Configure ''infinispan.client.hotrod.statistics=true" in the hotrod-client.properties
or
- Configure by code, for example:

@Bean
public InfinispanRemoteConfigurer infinispanRemoteConfigurer() {
    return () -> new ConfigurationBuilder().statistics().enable().build();
}

JMX

If you want to use Infinispan and JMX, for example on Client/Server mode, set the 'jmx' property 'true' as explained above with the 'statistics' property. However, you might get a javax.management.InstanceAlreadyExistsException because both Infinispan and Spring will try to register the MXBean.

The correction will land on the next starter release. If you need to avoid this error today, you can tell Spring-Boot not to register the bean with the following code (Thanks Stéphane Nicoll for the tip!):


Testcontainers

This version includes an integration test using Testcontainers, JUnit5 and the Infinispan Server. Grab a look here if you are curious.


1.0.7.Final


1.0.7.Final upgrades to 1.5.19.RELEASE and Infinispan 9.4.11.Final.

⭐ Don't forget to star the project in GitHub if you like the starter! ⭐

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

Thursday, 7 March 2019

Subatomic Infinispan Client

Today, the Quarkus project was released as a public beta. https://quarkus.io/ For those of you not familiar, Quarkus allows you to write your enterprise apps as you have done in the past with Hibernate/JAX-RS, but also to compile these applications to a Graal-VM native image. Running in a native image allows for the application to be started up in mere milliseconds, depending upon the app, all while using much less memory.

The Infinispan team is proud to announce that you can use the HotRod Java client in Quarkus and supports being compiled to a native image as well. This can allow you to startup and connect to a remote Infinispan server faster than ever before.

If you want a quick and simple example of how you can get this working you can take a look at the quick start which can be found at https://github.com/quarkusio/quarkus-quickstarts/tree/master/infinispan-client. This example covers configuring the client connection, cache injection and simple get/put operations as a basis.

The Infinispan Client Quarkus extension in addition to providing an easy way to create a Graal-VM native image with Infinispan Client also provides the following features to help the user get stuff done quicker.
  1. Automatically Inject Important Resources
    1. RemoteCache (named)
    2. RemoteCacheManger
    3. CounterManager
  2. User based ProtoStream Marshalling
  3. Querying (Indexed / Non Indexed)
  4. Continuous Query
  5. Near Cache
  6. Authentication/Authorization
  7. Encryption
  8. Counters

More details for these features as well as how to configure them can be found at https://quarkus.io/guides/infinispan-client-guide

Please let us know of any questions, concerns or suggestions at the usual places: forum or chat. We expect to continue enhancing this extension and would love to have any feedback.

Wednesday, 6 March 2019

Triple cachestore release: Cloud, MongoDB and Cassandra

Today we present to you a trifecta of cache store releases which align to Infinispan 9.x

Cassandra Cache Store

The Cassandra cache store now implements the publishEntries/publishKeys methods.

Cloud Cache Store

The Cloud cache store uses the Apache jclouds library to store data on cloud storage providers such as Amazon’s S3, Rackspace’s Cloudfiles or any other such provider supported by JClouds.
The store has been updated to Infinispan 9.x's persistence SPI and uses jclouds 2.1.x

MongoDB Cache Store

This cache store has also been updated to the Infinispan 9.x persistence SPI.

You can get documentation and maven coordinates from our Cache Store page

Tuesday, 5 March 2019

Enhanced JGroups configuration

Infinispan uses JGroups as its underlying clustering layer. In order to configure the finer details of clustering (discovery, flow control, cross-site, etc) you have to provide a separate XML file with the desired configuration and reference it from your Infinispan XML file as follows:


For simple configurations this is usually fine, but configuring complex setups, such as cross-site replication, means juggling multiple files (one for the local stack, one for the cross-site stack and one for the relay configuration).

Starting with Infinispan 10 Alpha2 we have introduced a number of changes to make your life with JGroups configurations a lot easier.

Default stacks

Infinispan now comes with two pre-declared stacks: tcp and udp. Using them is as simple as just referencing their names in the <transport> element.

Inline stacks

Inlining a stack means you can put the JGroups configuration inside the Infinispan one as follows:

You can use the full JGroups schema, and by using XML namespaces you get full validation.

Stack inheritance

Most of the time you want to reuse one of the pre-declared stacks but just override some of the parameters (e.g. discovery) to suit your environment. The following example creates a new tcpgossip stack which is based on the default tcp stack but replaces the discovery protocol with TCPGOSSIP:


In the above example you can see that we have enhanced the JGroups protocol declarations with two new attributes: ispn:stack.combine and ispn:stack.position which affect how and where protocol changes are applied on the parent configuration to obtain a new configuration. stack.combine can be one of COMBINE (the default, possibly overriding any specified attributes), REPLACE (which completely replaces the protocol and resets all attributes), REMOVE (removes the protocol) and INSERT_AFTER (which places this protocol in the stack immediately after the protocol specified by stack.position).

Multiple stacks and Cross-site

The inline configuration really shows its usefulness in cross-site configurations. In fact, the JGroups stack declaration has been extended with a special element which replaces the need for a separate relay XML file and can reference other stacks just by name. The following configuration uses the default udp stack for the local cluster transport and uses the default tcp stack for connecting to a remote site:

Having the entire configuration in a single place greatly simplifies management. Of course you can combine all of the above features to obtain the configuration you need for your environment. You can find more details and examples in the documentation.
Enjoy !
Tristan

Monday, 4 March 2019

First OpenShift Operator pre-release for Infinispan is here!

Infinispan Operator is a new method of packaging, deploying and managing Infinispan clusters on OpenShift. You can think of the Infinispan Operator as the runtime that manages Infinispan clusters on OpenShift.

We've just done our first Infinispan Operator pre-release, version 0.1.0, which allows you to easily boot up an Infinispan cluster on OpenShift.

Using the operator is as simple as installing the Infinispan Operator (requires admin access) on OpenShift, and then create a YAML descriptor that defines the Infinispan cluster. The example below shows how to create a 3-node Infinispan cluster:

And then call:

$ oc apply -f example-infinispan.yaml

A more detailed tutorial on using the Infinispan Operator can be found here. We highly recommend you give it a go and let us know what you think.

Over the next few versions we'll be adding more features that make the most of the capabilities the Operator framework offers to automatically manage the health and status of running Infinispan clusters.

Please also note that as we work towards the 1.0 release, some things might change :)

Cheers
Galder

Friday, 22 February 2019

Infinispan Spring Boot Starter 2.1.4.Final is out!

Dear Infinispan and Spring Boot users,

We have just released Infinispan Spring Boot 2.1.4.Final.

2.1.4.Final is using the last Infinispan Release 9.4.8.Final and Spring-Boot 2.1.3.RELEASE.

You can find this release 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

Thursday, 21 February 2019

Infinispan 10.0.0.Beta2 and 9.4.8

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.

10.0.0.Beta2

The first beta of our next major release contains a number of enhancements:

[ISPN-9847] - Extend configuration to allow inline JGroups configuration and inheritance
[ISPN-9699] - Cluster member owning no data
[ISPN-8124] - ServerNG: Initial implementation

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

Notable fixes:

[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

9.4.8.Final

Our latest point release contains lots of bug fixes and minor enhancements.

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

Thursday, 31 January 2019

Infinispan Spring Boot Starter 2.1.3.Final is out!

Dear Infinispan and Spring Boot users,

We have just released Infinispan Spring Boot 2.1.3.Final.

2.1.3.Final is using the last Infinispan Release 9.4.6.Final and contains some bug fixes related to Actuator integration.

You can find this release 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

Monday, 28 January 2019

10.0.0.Alpha3 and 9.4.6.Final

Hey there,

the Infinispan team has cooked two releases for you today:

10.0.0.Alpha3

This release contains 3 features:


  • [ISPN-4075] - State transfer should preserve the creation timestamp of entries
  • [ISPN-9320] - Automatic hot rod client version selection
  • [ISPN-9625] - Make clustered locks configuration possible by XML
  • [ISPN-9771] - Support for configuration in JSON format
We've also started removing code which was deprecated in the past, so check the upgrading document to see what you need to adapt in your application. This document will receive further changes during the 10.0 cycle.

The complete list of issues resolved in 10.0.0.Alpha3.

Some other features are in the works and should be landing during the beta period. Check the first of the alpha posts to learn more about the new stuff.


9.4.6.Final

The stabilization of 9.4 continues with this micro release.

Highlights are:

  • [ISPN-7889] - BaseDistributionInterceptor.remoteGet may cause concurrency issues
    [ISPN-8889] - Data race in NonTxInvocationContext
  • [ISPN-9873] - Remove listeners when the lock is removed
  • [ISPN-9822] - BasicComponentRegistryImpl fails with security manager
  • [ISPN-9819] - Improve Spring-Session events handling in remote and embedded

The complete list of issues resolved in 9.4.6.Final.


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

Tuesday, 15 January 2019

Infinispan Spring Boot Starter 2.1.2.Final is out!

Dear Infinispan and Spring Boot users,

We have just released Infinispan Spring Boot 2.1.2.Final.

2.1.2.Final is using Spring Boot 2.1.2.RELEASE and contains some bug fixes related to JCache and Actuator integration.

The starter is now using Infinispan's last stable release: 9.4.5.Final.

You can find this release 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