Hi Ryan,
On Wed, Aug 13, 2014 at 10:00 PM, ryan walsh <[email protected]> wrote: > Hello all > > We have two clusters, cluster A and cluster B. > > Cluster A is a JMS consumer that uses clusterClient to send messages over > to B for processing. > > During load testing, we did the equivalent of a cold start, which caused > cluster A to lose contact with cluster B. At this point, many messages had > been delivered and cluster A was awaiting responses back from cluster B > with the results. > > > 08-13-2014 13:38:06,603 ClusterRemoteWatcher.apply$mcV$sp WARN - > Detected unreachable: [akka.tcp://[email protected]:24896] > 08-13-2014 13:38:06,635 ClusterClient.apply$mcV$sp INFO - Lost > contact with [Actor[akka.tcp:// > [email protected]:24896/user/receptionist#-1548308322]], restablishing > connection > > 08-13-2014 13:38:06,793 Remoting.apply$mcV$sp WARN - Tried to associate > with unreachable remote address [akka.tcp://[email protected]:24896]. > Address is now gated for 5000 ms, all messages to this address will be > delivered to dead letters. Reason: The remote system has a UID that has > been quarantined. Association aborted. > > 08-13-2014 13:38:06,874 ClusterClient.apply$mcV$sp INFO - Connected to > [akka.tcp://[email protected]:24896/user/receptionist] > > We then looked at cluster B's logs, it also has disassociated. > > > 08/13/2014 13:38:06,763 WARN [ClusterB-akka.actor.default-dispatcher-5] > Remoting - Tried to associate with unreachable remote address [akka.tcp:// > [email protected]:23616]. Address is now gated for 5000 ms, all messages > to this address will be delivered to dead letters. Reason: The remote > system has quarantined this system. No further associations to the remote > system are possible until this system is restarted. > > My question is when reconnected, how do we get the responses from Command > B to send back to Cluster A? It appears that it getting sent to deadletters > is preventing the responses from ever getting sent back. Is there a way to > get these responses sent back to the reconnected cluster? > That is not possible automagically. The responses are sent back via ActorRefs pointing to actors that are now stopped. You must somehow retry, or re-register, with your new actor instances in the restarted ClusterA and let ClusterB send back the result again. A side note: make sure you use latest Akka 2.3.5, since we had issues with remote watch in < 2.3.3. /Patrik > > -- > >>>>>>>>>> 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. > -- Patrik Nordwall Typesafe <http://typesafe.com/> - Reactive apps on the JVM Twitter: @patriknw -- >>>>>>>>>> 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.
