Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Thoughts on redundant Actors
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Derek Wyatt  
View profile  
 More options Feb 10, 10:31 am
From: Derek Wyatt <de...@derekwyatt.org>
Date: Fri, 10 Feb 2012 10:31:33 -0500
Local: Fri, Feb 10 2012 10:31 am
Subject: Thoughts on redundant Actors

Hi guys,

I've been thinking about a system for redundant Actors and I'm wondering
what thoughts people would have with respect to existing functionality in
Akka.

I need to have a primary Actor on a machine, with a secondary on another
machine and a tertiary on another machine in another region of the world.
My plan is to have upstream components send the same message to all three
Actors but only one of them will be primary.  The Actors are holding data
that is to be picked up by someone "later", thus private Actor data is
'interesting'.

- Obviously if the primary goes down, then the secondary needs to become
primary.
- If the secondary or tertiary go down, we need to replace them.
- The data need to be kept "in sync" (yes, that's a very hairy topic...
assume it's easy for the moment :D).

My plan is to have the supervisor be some Actor on the physical machine but
set up DeathWatch between the three Actors so that they can take action
should any of them kick the bucket.

I haven't seen anything yet that really applies to this - obviously
clustering would be a good candidate for this sort of deal but that's gonna
have to wait.  Is there anything in the meantime that I might be able to
leverage?  Or should I just put something together myself?

Thx,
Derek


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »