Re: [akka-user] Configuration Compatibility Check ignored when using Cluster(system).join(address)

Thank you Patrick, I see this behavior is expected. Considering joining a cluster manually, what is the difference between the joinSeedNodes and the join processes? What makes the join process so different that nodes' configurations do not need to be checked for compatibility? Thanks, Fred On

Re: [akka-user] Configuration Compatibility Check ignored when using Cluster(system).join(address)

It’s only part of the joinSeedNodes process. Perhaps that is missing in docs, and contribution fixing that is welcome. /Patrik lör 24 feb. 2018 kl. 18:13 skrev Frederic : > Hello all, > > I've just done a few tests with the new Configuration Compatibility Check > and

[akka-user] Re: Help wanted: Distributed Data with akka-typed, java and Akka 2.5.10

I solved it for now using asScala() ActorRef> readResponseAdapter = ctx.asScala().spawnMessageAdapter(InternalGetResponse::new); ActorRef> updateResponseAdapter = ctx.asScala().spawnMessageAdapter(msg -> new

[akka-user] Akka HTTP: How to find out that there is no Content-Type header?

Hey, Akka HTTP experts, Akka HTTP treats the Content-Type header in a special way (seemingly according to the spedification). In particular if the request contains neither a Content-Type header nor entity data, it sets the Content-Type to "application/octet-stream“. This seems to be in sync

[akka-user] Configuration Compatibility Check ignored when using Cluster(system).join(address)

Hello all, I've just done a few tests with the new Configuration Compatibility Check and noticed that no compatibility check is performed (aka checks are ignored) when joining the cluster manually using Cluster(system).join(address). Is that expected? I didn't find any documentation