That explains it. Serializer 9 is DistributedPubSubMessageSerializer
Serialization errors are not transient (that is changed in new remoting
Artery). See this ticket for discussion
https://github.com/akka/akka/issues/20641
In your case you have not included the distribute-data jar in the
Hi,
Please see the logs attached. The logs are directly taken from Kibana so
the formatting is not great.
On a side note we are running each of our component inside a docker
container on AWS.
Thank you,
Philippe
The main hint for us when this happens is when we see the following
exception:
Hi Philippe,
You can use the cluster node role to use pub-sub on a subset of nodes. You
have to start the extension on all nodes with the given role.
I would be interested in taking a look at the logs from such a "crash". I
would expect that messages would be dropped, but nothing more. I would
Hello,
We are new at using Akka in general. So far we managed to create a cluster
with the following components:
Seeds
Cluster-manager (simply display the status of componenents)
Backend
Frontend
Recently we decided to add the pubsub extension to the backend and
frontend. However introducing
