Hi Filippo, One idea (of many I guess):
1. Have a dispatcher for long running futures. 2. For each task create an actor and within that actor create a future that each time such task status changes it sends a message to its actor. 3. Query such actor to get statuses. The reason that you need an actor and a future is because an actor can do one thing at the time so you wouldn't be able to execute the job and query status at the same time, HTH, Guido. On Wednesday, March 16, 2016 at 10:02:25 PM UTC, Filippo De Luca wrote: > > Hi Guys, > I have a task to schedule a long term task on the cluster. I am thinking > to model this task as an Actor that got deployed remotely. What is the best > approach to do that? > I want to have a way to control the amount of concurrent process I run in > the cluster. > > Also the Actor that run the process, run it in a Future, and it only > monitor it by receiving update on the progress from the future. Should I > use a child actor instead? The idea is that, the actor should be query-able > to ask the progress status. > > Any help will be very welcome. > > > -- >>>>>>>>>> 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.
