From efe02935cdcefd0055f9c74d9af0b705afdd156b Mon Sep 17 00:00:00 2001 From: Patrik Nordwall Date: Tue, 18 Aug 2020 15:16:44 +0200 Subject: [PATCH] doc: rolling update from 2.5.x to 2.6.2 (#29501) --- .../src/main/paradox/project/migration-guide-2.5.x-2.6.x.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/akka-docs/src/main/paradox/project/migration-guide-2.5.x-2.6.x.md b/akka-docs/src/main/paradox/project/migration-guide-2.5.x-2.6.x.md index 6413f37f0f..3d2e5874ee 100644 --- a/akka-docs/src/main/paradox/project/migration-guide-2.5.x-2.6.x.md +++ b/akka-docs/src/main/paradox/project/migration-guide-2.5.x-2.6.x.md @@ -19,7 +19,9 @@ reading this migration guide and testing your application thoroughly is recommen Rolling updates are possible without shutting down all nodes of the Akka Cluster, but will require configuration adjustments as described in the @ref:[Remoting](#remoting) section of this migration -guide. +guide. Due to the @ref:[changed serialization of the Cluster messages in Akka 2.6.2](rolling-update.md#2-6-2-clustermessageserializer-manifests-change) +a rolling update from 2.5.x must first be made to Akka 2.6.2 and then a second rolling update can change to Akka 2.6.3 +or later. ## Scala 2.11 no longer supported