Thank you Endre!
"This can result from two reasons as far as I see:
A) there is no actor on that path.
B) the ActorRef you use to send is referring to an older actor and the UID
does not match with the new instance."
I don't think either of these things are the case - the worker is only
created at startup, and you can see in the output that the worker is
responding to periodic pings.
DEBUG [2015-10-01 09:01:35,261] [] [] [dispatcher-4] c.t.a.cluster.Worker
akka.tcp://ClusterSystem@SLAVEIP:12489/user/worker - Worker with path
akka://ClusterSystem/user/worker received ping.
*I could better verify this if there were some way for the worker to log
its UID when it gets the ping. I am not finding a way to do that. Is it
possible?*
Also, currently I have the master addressing the worker in two ways:
workers.foreach {
case (_, WorkerState(ref, Idle)) => {
log.debug(s"Master sending $work to $ref with path ${ref.path}")
ref ! work
context.actorSelection(ref.path) ! work
}
case _ => // busy
}
Both go to Dead Letters
WORKER SYSTEM: INFO [2015-10-01 09:01:31,823] [] [] [dispatcher-4]
a.a.EmptyLocalActorRef akka://ClusterSystem/user/worker - Message
[mycompany.akka.cluster.Work] from
Actor[akka.tcp://ClusterSystem@MASTERIP:12487/user/master/singleton#-83415853]
to Actor[akka://ClusterSystem/user/worker#-2093331180] was not delivered.
[1] dead letters encountered. This logging can be turned off or adjusted
with configuration settings 'akka.log-dead-letters' and
'akka.log-dead-letters-during-shutdown'.
WORKER SYSTEM: INFO [2015-10-01 09:01:31,831] [] [] [dispatcher-3]
a.a.EmptyLocalActorRef akka://ClusterSystem/user/worker - Message
[mycompany.akka.cluster.Work] from
Actor[akka.tcp://ClusterSystem@MASTERIP:12487/user/master/singleton#-83415853]
to Actor[akka://ClusterSystem/user/worker] was not delivered. [2] dead
letters encountered. This logging can be turned off or adjusted with
configuration settings 'akka.log-dead-letters' and
'akka.log-dead-letters-during-shutdown'.
Also, these are not on the same JVM. They are on separate AWS instances.
I will bump up logging (so far, that hasn't really given me any more
insight, but if there's some way to output the UID, please let me know -
that would be helpful. If nothing comes of that, I'll try to create a
scaled down version, but unfortunately, the core of the joinSeedNodes code
relies on an internal service discovery tool, so that will be less than a
perfect match.
Thanks!
--
>>>>>>>>>> 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.
