Hi all.

I'm trying a hot swap between an active processor and a backup one, in line 
with the 
this<https://www.assembla.com/spaces/akka/tickets/3938#/activity/ticket:> 
ticket, 
to avoid delay while swapping huge actors. 

I'm thinking about manually sending my commands to two different actors in 
a active/passive fashion. In case of node failure I'd like to point out to 
the passive instance, avoiding startup delay. I'm thinking about having two 
sharding regions and then, after node failure and using a particular 
sharding strategy, point out to the node where the passive object is. Maybe 
the hotswap (as decribed 
here<http://doc.akka.io/docs/akka/snapshot/java/untyped-actors.html#untypedactor-hotswap>)
 
can be used to deviate the commands to passive actor. In the meanwhile the 
standard Akka persistence scheme is being used to re-initiate the original 
actor that could be used later after a new node failure. 

Do you think that this approach is feasible or maybe there is another 
simpler way to achieve this behavior? 

Many thanks for your help.

Eduardo.

-- 
>>>>>>>>>>      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 http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to