Skip to main content

Unomi 4.0 ships a modern runtime with the rest of the major release: fewer legacies, clearer installers, and a cluster model that matches how Unomi already stores data.

Unomi 4.0 runtime: Java 17, Karaf 4.4, search clients, persistence clustering

Baseline upgrades

  • Java 17+ — Java 11 is retired for Unomi 4 installers and CI
  • Apache Karaf 4.4 — current patch lines (for example 4.4.11)
  • Elasticsearch 9 — Java API client; HLRC retired; OpenSearch as a peer distribution (see Elasticsearch 9 and OpenSearch)
  • Log / dependency pins — platform bump PRs keep Log4j and client stacks on supported lines

Persistence-based clustering (UNOMI-877)

Cellar and Hazelcast are gone. Nodes register ClusterNode documents in Elasticsearch or OpenSearch, publish heartbeats and stats, and discover peers through the shared index. The same mechanism underpins executor selection and locking for the cluster-aware task scheduler.

What operators should do

Treat 4.0 as the cutover from 2.x: confirm Java 17 hosts, pick an ES9 or OpenSearch distribution, and read the clustering and health-check chapters together with tenants and tasks. The migrating from 2.x post covers the REST and auth cutover; the manual holds the day-two runbooks.

Manual: clustering What’s new Introducing Unomi 4

← All posts