You're welcome. Yes, you are supposed to register (start) the sharding on
all nodes (or nodes with a certain role). The coordinator is a Cluster
Singleton, i.e. running on oldest node (when you have started it). Other
nodes try to register to the coordinator at the oldest node.
/Patrik
tis 1 aug.
Thanks for the prompt reply. As hoped it has instantly made me realize the
error of our ways.
Our application bootstrap code was over using lazy val's, so as you suggest
we weren't actually calling ClusterSharding.start until that node needed
the ActorRef.
So I can further my understanding, co
Looks like ClusterSharding.start is missing at startup of api-0. Are you
sure that you do that when the ActorSystem has been started and not lazily
on first request?
Enable debug level logging and you should see what it is doing. You should
see log entries in api-0 at startup.
/Patrik
tis 1 aug.
As a follow up, I've now just ruled out any kubernetes networking issue by
recreating the same behaviour running 3 nodes via docker-compose instead -
again it only works if an API call hits the first node in seed-nodes list.
On Tuesday, 1 August 2017 14:11:07 UTC+1, Stephen Kennedy wrote:
>
> Hi
