Thx for confirmation. I have a concern though and I cannot distil a clear answer from docs. In my case nodes are quite independent actually and they can go down and up as wish. This is not exception, this is part of the design.
I played with actors like a year ago and remember that once a remote goes down, the "client" hangs and get confused. It is not like all messages are dropped due to missing destination mailbox. I also wonder about remote Actor lookup by name, is it going to timeout or fail instantly (since remote is down). Would it get worse if large number of messages are to be send to that node which is down? I also wanted to be able to add nodes dynamically. I just start a new one pointing to another member of the network, it automagically registers itself in the network and starts working i.e. taking/sending updates from/to nearest nodes. Is something like that possible? A. On Wed, Jan 22, 2014 at 9:21 AM, Patrik Nordwall <[email protected]>wrote: > It looks like a perfect match for Akka Cluster for the functional > requirements as well. > /Patrik > > > On Wed, Jan 22, 2014 at 5:05 PM, √iktor Ҡlang <[email protected]>wrote: > >> >> http://typesafe.com/blog/running-a-2400-akka-nodes-cluster-on-google-compute-engine >> >> >> On Wed, Jan 22, 2014 at 4:46 PM, Andy C <[email protected]> wrote: >> >>> Hi, >>> >>> My application has following requirements and I was wondering if Akka >>> Actors is something I could use: >>> >>> 1) I need to use between 8 to 32 remote machines aka nodes >>> 2) There is no single server, they are more like fully symmetrical nodes >>> 3) Nodes are about send messages between them providing updates, also >>> node might generate original update which needs to at some point reach >>> other nodes >>> 4) Updates might take time to propagate, it is not necessary to have all >>> nodes be in sync all the time >>> 5) However, in order to avoid the situation that all nodes are talking >>> to each other, it would be more like one node exchange updates with nearest >>> three or four, in a way that there is always path between every two ones, >>> in a way similar to http://en.wikipedia.org/wiki/Token_ring >>> 6) If a one node goes down, no other one will time out, get stuck or be >>> impacted one way or another >>> 7) Also, if given node wakes up, it will seamlessly join the network and >>> start receiving updates >>> 9) Every update will carry a "depth" counter going down to prevent the >>> update circulating in the above network. Once "depth" reaches 0, it will be >>> abandoned. Initial value represents a length of a longest path between nodes >>> A) Every node will maintain only most recent updates, so there is no >>> need to "replay" old updates. >>> >>> In another words, this would model a best effort, distributed state >>> system. I probably could just use a thin layer over UPD, however I really >>> like all the semantics behind Actors. >>> >>> Would Akka fit here? >>> >>> Thx, >>> Andy >>> >>> -- >>> >>>>>>>>>> Read the docs: http://akka.io/docs/ >>> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>> >>>>>>>>>> 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/groups/opt_out. >>> >> >> >> >> -- >> Cheers, >> √ >> >> * ——————— **Viktor Klang* >> *Chief Architect - **Typesafe <http://www.typesafe.com/>* >> >> Twitter: @viktorklang >> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >> >>>>>>>>>> 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/groups/opt_out. >> > > > > -- > > Patrik Nordwall > Typesafe <http://typesafe.com/> - Reactive apps on the JVM > Twitter: @patriknw > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: http://akka.io/faq/ > >>>>>>>>>> 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/groups/opt_out. > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
