From 8df2366284aa162f5e9e7072f4db2927604e87c7 Mon Sep 17 00:00:00 2001 From: Patrik Nordwall Date: Thu, 4 Apr 2019 09:09:52 +0200 Subject: [PATCH] addition about rolling update in Artery migration guide (#26670) --- akka-docs/src/main/paradox/project/rolling-update.md | 3 +++ akka-docs/src/main/paradox/remoting-artery.md | 3 +++ 2 files changed, 6 insertions(+) diff --git a/akka-docs/src/main/paradox/project/rolling-update.md b/akka-docs/src/main/paradox/project/rolling-update.md index 674161987d..35d852604b 100644 --- a/akka-docs/src/main/paradox/project/rolling-update.md +++ b/akka-docs/src/main/paradox/project/rolling-update.md @@ -26,6 +26,9 @@ For example it's possible to update from 2.5.14 to 2.5.16 without intermediate 2 It's not supported to have a cluster with more than two different versions. Roll out the first update completely before starting next update. +Rolling update from classic remoting to Artery is not supported since the protocol +is completely different. It will require a full cluster shutdown and new startup. + ## Shutdown order It's best to keep the node that has been running the longest until last. That is because diff --git a/akka-docs/src/main/paradox/remoting-artery.md b/akka-docs/src/main/paradox/remoting-artery.md index c5f0c1fc31..a611c2123e 100644 --- a/akka-docs/src/main/paradox/remoting-artery.md +++ b/akka-docs/src/main/paradox/remoting-artery.md @@ -131,6 +131,9 @@ The configuration is different, so you might have to revisit any custom configur @ref:[reference configuration for Artery](general/configuration.md#config-akka-remote-artery) and @ref:[reference configuration for classic remoting](general/configuration.md#config-akka-remote). +One thing to be aware of is that rolling update from classic remoting to Artery is not supported since the protocol +is completely different. It will require a full cluster shutdown and new startup. + ## Canonical address In order to remoting to work properly, where each system can send messages to any other system on the same network