Re: [akka-user] Cluster failover: preloaded actors
You're welcome. Anyway, I have created a ticket for the hot standby processor: https://www.assembla.com/spaces/akka/tickets/3938 That doesn't mean that we will implement it, but we will take it into consideration. Thanks for the feedback. Cheers, Patrik On Tue, Mar 18, 2014 at 8:52 PM, Eduardo Fernandes edu...@gmail.com wrote: Many thanks Patrik for your post. Good shot. We could consider sending commands simultaneously to two processors (the main and a standby) and in case of timeout talking to the first we could talk to the second. After the main recovering we could return to the original situation. Maybe we could create both actors in different clusters in different machines to avoid single point of failure in case of machine crash. Many thanks again for your time and for any comment. Regards. El martes, 18 de marzo de 2014 17:12:43 UTC+1, Patrik Nordwall escribió: I see what you are looking for, and it is not supported with current tools. It would be something that is periodically replaying the event stream like a view, but can then be changed into a normal writing processor. Have you thought about using an active standby? It would do the exact same thing as the primary, but the output (external side effects) would be ignored/filtered on the standby. It depends very much on your domain if that is a good or bad idea. Regards, Patrik -- 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. -- Patrik Nordwall Typesafe http://typesafe.com/ - Reactive apps on the JVM Twitter: @patriknw -- 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.
Re: [akka-user] Cluster failover: preloaded actors
Thanks for the new ticket! This kind of behavior is extremely useful in some cases. In our case we're moving huge Redis/HBase structures to multiple java/scala maps and the result is thousand of times faster and simple and faster to implement. We think, after reading the docs, that Akka is a half step away of this. Thanks again for your help and time! El miércoles, 19 de marzo de 2014 09:30:15 UTC+1, Patrik Nordwall escribió: You're welcome. Anyway, I have created a ticket for the hot standby processor: https://www.assembla.com/spaces/akka/tickets/3938 That doesn't mean that we will implement it, but we will take it into consideration. Thanks for the feedback. Cheers, Patrik On Tue, Mar 18, 2014 at 8:52 PM, Eduardo Fernandes edu...@gmail.comjavascript: wrote: Many thanks Patrik for your post. Good shot. We could consider sending commands simultaneously to two processors (the main and a standby) and in case of timeout talking to the first we could talk to the second. After the main recovering we could return to the original situation. Maybe we could create both actors in different clusters in different machines to avoid single point of failure in case of machine crash. Many thanks again for your time and for any comment. Regards. El martes, 18 de marzo de 2014 17:12:43 UTC+1, Patrik Nordwall escribió: I see what you are looking for, and it is not supported with current tools. It would be something that is periodically replaying the event stream like a view, but can then be changed into a normal writing processor. Have you thought about using an active standby? It would do the exact same thing as the primary, but the output (external side effects) would be ignored/filtered on the standby. It depends very much on your domain if that is a good or bad idea. Regards, Patrik -- 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+...@googlegroups.com javascript:. To post to this group, send email to akka...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- Patrik Nordwall Typesafe http://typesafe.com/ - Reactive apps on the JVM Twitter: @patriknw -- 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.
Re: [akka-user] Cluster failover: preloaded actors
Hi, On Tue, Mar 18, 2014 at 11:45 AM, Eduardo Fernandes edu...@gmail.comwrote: Hi All. First of all many thanks for so efficient library. Very good job! We're analyzing Akka to support a cluster of heavy objects (a single actor could have a couple of gigs in RAM). I'm wondering if I could use some kind of 'preloaded' in ram slave actor that could be used if the 'master actor' fails. It would be something like an updated View or something like that which gets the main role after a failure. The journal and snapshots are ok but I'm afraid that the recovering time could be minimized if I used the 'slave' idea for heavy actors. After the backup object gets the main role a new 'slave' should be created from a normal snapshot and it would be prepared for the next failover cycle. I see what you are looking for, and it is not supported with current tools. It would be something that is periodically replaying the event stream like a view, but can then be changed into a normal writing processor. Have you thought about using an active standby? It would do the exact same thing as the primary, but the output (external side effects) would be ignored/filtered on the standby. It depends very much on your domain if that is a good or bad idea. Regards, Patrik I've tried to find out in the docs something to help me with this without success. Many thanks in advance for your help! -- 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. -- Patrik Nordwall Typesafe http://typesafe.com/ - Reactive apps on the JVM Twitter: @patriknw -- 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.
Re: [akka-user] Cluster failover: preloaded actors
Many thanks Patrik for your post. Good shot. We could consider sending commands simultaneously to two processors (the main and a standby) and in case of timeout talking to the first we could talk to the second. After the main recovering we could return to the original situation. Maybe we could create both actors in different clusters in different machines to avoid single point of failure in case of machine crash. Many thanks again for your time and for any comment. Regards. El martes, 18 de marzo de 2014 17:12:43 UTC+1, Patrik Nordwall escribió: I see what you are looking for, and it is not supported with current tools. It would be something that is periodically replaying the event stream like a view, but can then be changed into a normal writing processor. Have you thought about using an active standby? It would do the exact same thing as the primary, but the output (external side effects) would be ignored/filtered on the standby. It depends very much on your domain if that is a good or bad idea. Regards, Patrik -- 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.