I just remembered one thing we forgot, we should add documentation on how to actually perform the rolling release migration from akka to pekko nodes, i.e. adjusting the accept-protocol-names so it contains both pekko and akka (this is default) and setting protocol-name = to akka (so that pekko and akka nodes can communicate with eachother), perform the rolling release upgrade and then when all akka nodes are shut down set the protocol-name to pekko to perform the second rolling update.
On Wed, Jan 24, 2024 at 9:15 AM PJ Fanning <fannin...@apache.org> wrote: > Hi everyone, > > I've started a separate thread about a possible 1.1.0-M1 release but I > would also like to discuss a 1.0.3-M1 release. We have some changes > already merged but there is a more experimental set of changes that I > would like to see in a milestone release to support mixed Akka and > Pekko clusters. > > The extra PR that is probably not safe enough for a full release but > useful in a milestone release is: > https://github.com/apache/incubator-pekko/pull/765 > > Another PR that is merged but not yet released is: > https://github.com/apache/incubator-pekko/pull/841 > > Any thoughts or objections to doing a 1.0.3-M1 that allows users to > try out mixed Akka and Pekko clusters? > > Regards, > PJ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > For additional commands, e-mail: dev-h...@pekko.apache.org > > -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Alexanderufer 3-7, 10117 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* matthew.dedetr...@aiven.io
