Skip to content

Latest commit

 

History

History
51 lines (38 loc) · 2.26 KB

release_notes_340.md

File metadata and controls

51 lines (38 loc) · 2.26 KB
title tags published keywords summary permalink
Release notes 3.4.0
release_notes
true
release notes, announcements, changelog
Version 3.4.0 of Eclipse Ditto, released on 13.09.2023
release_notes_340.html

The fourth minor release of Ditto 3.x, Eclipse Ditto version 3.4.0 is here.

This release is completely IP (intellectual property) checked by the Eclipse Foundation meaning that project code as well as all used dependencies were "[...] reviewed to ensure that the copyrights expressed are correct, licensing is valid and compatible, and that other issues have been uncovered and properly investigated."

Changelog

Compared to the latest release 3.3.6, no features were added. This release focuses only on swapping the Akka framework (because of its switch of license to BSL License after Akka v2.6.x) with its fork Apache Pekko which is Apache 2.0 licensed.

Migrating to Ditto 3.4.x

To migrate a running system with live data there are few configurations that should be overridden with Java system properties in the following services.

Policies:

* -Dpekko-contrib-mongodb-persistence-policies-journal.overrides.metadata-index=akka_persistence_metadata_pid
* -Dpekko-contrib-mongodb-persistence-policies-journal-read.overrides.metadata-index=akka_persistence_metadata_pid

Things:

* -Dpekko-contrib-mongodb-persistence-things-journal.overrides.metadata-index=akka_persistence_metadata_pid
* -Dpekko-contrib-mongodb-persistence-things-journal-read.overrides.metadata-index=akka_persistence_metadata_pid

Connectivity:

* -Dpekko-contrib-mongodb-persistence-connection-journal.overrides.metadata-index=akka_persistence_metadata_pid
* -Dpekko-contrib-mongodb-persistence-connection-journal-read.overrides.metadata-index=akka_persistence_metadata_pid
* -Dpekko-contrib-mongodb-persistence-connection-remember-journal.overrides.metadata-index=akka_persistence_metadata_pid

And also a full cluster recreate is required, rolling update is not supported as there are changes in the management urls and ports.

Other than that the transition should be smooth.