Skip to Content

Changes for page V3.3.0

Last modified by Erik Bakker on 2025/03/28 12:26
From version 3.1
edited by Carlijn Kokkeler
on 2024/01/15 11:22
Change comment: There is no comment for this version
To version 2.1
edited by Eva Torken
on 2024/01/11 11:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -V2.1.0
1 +V2.0.2
Parent
... ... @@ -1,1 +1,0 @@
1 -Main.Release Information.Runtime Images.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.etorken
Content
... ... @@ -2,18 +2,10 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  These are the release notes for this runtime image. Once a runtime image is released, every new release will utilize this runtime image as base for creating runtime images for docker. For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +=====Bug Fixes=====
6 6  
7 -New components to support a failover setup:
7 +* Crash handling is improved so that log messages clearly show when and why a container failed to start.
8 +* A bug is fixed in which no new log messages were showing up, even though they were produced by a container.
8 8  
9 -* Clustered lock registry: obtain a locks that can be shared over different containers
10 -* Leader initiator: Used to automatically start and stop roles based on whether they can obtain a cluster-wide lock
11 -* New & extended operations for controlling integration components
12 -** New: Start & stop all components in a specific role, so you can start and stop multiple components at the same time
13 -** New: List all roles and whether they support leadership
14 -** Extended: List flow components now also shows whether a component is configured to be in a role
15 -
16 -Deploy - Deployment plan: to incorporate failover actions during deployment, two new deployment step types are introduced namely “Group” and “Failover”.
17 -
18 18  )))((({{toc/}}))){{/container}}
19 19  {{/container}}