On Sunday, January 19, 2014 4:22:14 PM UTC, Jatin Puri wrote: > > Alistait, > > >> I'm not clear on how your cache is intended to work, but if the juniors >> are holding the cached data and the leader provides the updates, then the >> consequence of disconnection is that the junior will serve up out-of-date >> data. How dangerous this is depends on what the data is being used for. >> > > Ok. > >> >> I don't understand the comment about 'single attempt'. Who's attempting >> what here? >> > > So currently I am sending an update to `junior` and expect a return in a > second. If I do not get the response in a second, then I try again and keep > trying till 5th attempt. When even that fails, I mark it as failure. > > But then again I think that this redundancy is just unnecessary increase > in internal traffic. If it doesn't succeed in one attempt, I am not sure if > future attemps should be made. What do you think of it? > I think it's reasonable to retry until the deathwatch tells you that the junior is dead (or unreachable) - in other words, let the Akka mechanism decide when it's right to give up. It might be a good idea to increase the retry interval on every attempt (1 second, 2, 4, 8...) .
Cheers Alistair -- >>>>>>>>>> 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.
