I'm using akka cluster sharding to build for *a long connection streaming *distributed calculation engine. It's driven by request, basically for each request, there will be one entity actor started for calculation of that request, and this is a streaming request, which means the calculation actor will generate endless calculation result and sending back to client.
How should I do rolling update in this case to avoid data interrupt to the client? I am thinking of this way: 1. set remember-entities to on 2. upgrade application node by node, when some node is upgrading, all entities will be re-balanced to other available nodes so there should be a very short time outage(time cost for moving actor) for the calculation. 3. after all nodes have been upgraded, auto re-balance will be happened again to balance the load to the whole cluster. Is this an feasible solution? And another question which bother me is that with "remember-entites" is set to "on", I can't find a place to call *shardRegion.tell(ShardRegion.gracefulShutdownInstance(), null);* to really shutdown all entites in the shard region? Thank you. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
