We are considering using the DistributedPubSub support in a production system. We would like to be able to upgrade this system on the fly. I am trying to get some advice on that sort of setup. What we've seen is that when a node dies, we definitely have missed messages. However, when I issue the "leave" command (via JMX), things appear to clean up gracefully. Obviously, we would use the "leave" command in a production upgrade scenario, but is there anything we can do (other than setting up the at-least-once-delivery stuff) to get the cluster to more gracefully recover from a node failure? I've been playing around with this stuff using this very simple project on github:
https://github.com/jwcarman/akka-cluster-sandbox Basically, I've set it up so that there are three "seed" nodes, which I start up together. Then, I fire up the "client" node, which basically just sends strings to one of the seed nodes using a DistributedPubSubMediator.Send message. -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
