Akka.Cluster | Sample akka.net cluster project

I am facing java.lang.NullPointerException, while updating Akka version from 2.6.9 to 2.6.10.

Here's the sample code in which I am facing this error:-

1. akka-sharding/src/main/resources/application.conf

Im using distributed pub/sub in an Akka.net cluster and I've begun seeing this error when pub/sub grows to approx. 1000 subscribers and 3000 publishers.

max allowed size 128000 bytes, actual size of encoded Akka.Cluster.Tools.PublishSubscribe.Internal.Delta was 325691 bytes

I don't know, but I'm guessing distributed pub/sub is trying to pass the pub/sub list to other actor systems on the cluster?

Anyway, I'm a little hesitant about boosting size limits because of this post. So what would be a reasonable approach to correcting this?

I am attempting to make a project using Akka Clustering, and have been using the akka-cluster-sample-scala from Lightbend(https://github.com/akka/akka-samples/tree/2.6/akka-sample-cluster-scala) as a base. As it lacks much direct information on connecting across a network, I modified the application.conf to look more like this:

When I try to send a message to the akka.net region proxy with the following code,

According to the doc, it is recommended to implement efficient serialization with Protobuf or similar for our custom data type. However, I also find the built-in data types (e.g., GCounter) extends ReplicatedDataSerialization (see code), which according to scaladoc,

Marker trait for ReplicatedData serialized by akka.cluster.ddata.protobuf.ReplicatedDataSerializer.

I wonder whether I should implement my own serializer implementation or simply use the one from akka. What's the benefit of implementing my own? Since my custom data type implementation (see code or below) is really similar to a PNCounter I feel the Akka one would work for my case well.

Following the Ditto Deployment Docker description. E.g. Adding a new password and then executing Docker compose command. Starting with clean Linuxmint 19.3 and new installed Docker and Docker-Compose setup. The localhost:8080 is reachable but fails to load API definition (Fetch error). Additionally I tried Hello World Example - Creating a Thing with adjusted Password set by me and I receive the 502 Gateway. In another Stackoverflow question 502 Bad Gateway nginx/1.13.12 on localhost while creating a new policy in ditto there was mentioned to check docker-compose ps therefore I tried to attach everything in the screenshot. As I said this is clean install Linuxmint 19.3 (Linuxkernel: 5.0.0-37-generic x86_64, + Docker (Docker version 19.03.5) + Docker-Compose (docker-compose version 1.25.0) and then followed the deployment instructions. Anyone has some hints what need to be configured or where I can find more information to that issue? Thank you!

[EDIT]: 27/12/2019 Setup - clean Ubuntu 1910 + Docker + Docker-compose - services are up and running -> Do not get the Fetch error in the browser anymore but still getting 502 Gateway from Nginx when trying to use the REST-API (using Postman - Ditto Profile) -> See Screenshot (e.g. Creating Things ->still using the Hello World Example).

[EDIT: 02.01.2020] NGINX-LOG:

I am trying to run the Akka Distributed Workers project following the guide here https://developer.lightbend.com/guides/akka-distributed-workers-scala/

On run, it fails with series of error messages. The first one that caught my attention was:

I have a 3 node cluster with

1 S1 - Seed Node 2 S2 - A node that hosts a shard SRD (which has S1 as seed node in config) 3 S3 - A node that hosts the proxy shard of the shard hosted in S2 (which has S1 as seed node in config)

Here S1 just creates the actorsystem, and does nothing else

When I Start the cluster (S1 first, then S2 and S3) and When S3 tries to send a message to the shard SRD(using the proxyshard actor ref), it complains:

I'm building an app with two kind of nodes (front and back) on akka 2.5.1, I'm using akka sharding for load and data distribution across the back nodes. The front node uses a shard proxy to send messages to the back. Shards initialisation is as follow: