I’m using akka cluster, akka sharding and akka persistence for my system. When the system is running, I notice there is always a folder called ddata-{akka-system-name}-replicator-2551 created in the current working directory. I guess it’s used for storing akka persistence information, because if I experimentally delete the folder, my persistent actor cannot restore its state when the cluster restarts.
So my question here is if I deploy my akka cluster into Kubernetes, should I use k8s StatefulSet to use stable persistent volume to keep the ddata folder there between Pod restarts? I’ve referred to all akka kubernetes examples online, but all are using regular k8s stateless ReplicaSet/Deployment. I don’t find an akka persistence / k8s example so far.
5 posts - 3 participants