For us, the issue was ultimately a symptom of the problem referenced here: https://groups.google.com/forum/#!topic/akka-user/4lBUX7N7W6k
Our cluster was in a broken state and persistent actors were unable to recover. Patrik, if I read correctly this issue is resolved in 2.4? If so, would still like me to file a ticket Roland? On Thu, Jun 18, 2015 at 3:12 AM, Patrik Nordwall <[email protected]> wrote: > > > On Thu, Jun 18, 2015 at 11:46 AM, Brice Figureau < > [email protected]> wrote: > >> Hi, >> >> I'm also seeing this log message logged on a very unloaded cluster, on >> akka 2.3.11. >> >> On Wed, 2015-06-17 at 13:31 +0200, Patrik Nordwall wrote: >> > I'm interested in where all those resolve calls come from, because it >> > could be a performance issue. It could be deserialization of ActorRef. >> >> It's possible, but it is hard to confirm, since the log line doesn't >> give us a stacktrace to analyze. >> >> It seems to me that it appeared when I started using ClusterSingleton >> and ClusterSharding (but I can be wrong). Most of the references of this >> log line I see in my logs are for singletons endpoint or sharding >> entries. >> >> It looks like it happens approximately at the same time a persistent >> actor recovers (which would mean you found the real issue). >> > > Yes, that matches my understanding, and that will be solved in 2.4 > /Patrik > > >> >> > Yesterday I removed storage of the sender ActorRef in persistent >> > events, which typically would result in such things when persistent >> > actors replay the event log. >> >> Yes, that would make sense. >> >> > Does /user/token-mgr-proxy/TokenManager send messages to a persistent >> > actor, or do you know what is causing the failing resolve? >> >> I'll let the OP answer this question. >> >> -- >> Brice Figureau <[email protected]> >> >> -- >> >>>>>>>>>> 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 a topic in the > Google Groups "Akka User List" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/akka-user/qFGg0l9-fNg/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- >>>>>>>>>> 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.
